About the error log, maybe I could suggest a feature in future release to have error codes similar to Visual Basic?
So instead of the short generic message "Missing jar file..." which is kinda cryptic for newbie like me we could have something like, for example:
Error 300: An xml file is referencing a jar file that does not exist.
The file "D:\AdditionalLibraries\B4J\DataCollection.xml" is missing a matching jar file.
For detailed explanation about this error see the Manual at [this link].
And in the Manual the list of error codes can include possible scenarios why it happened, possible solutions, or tips to avoid having such issue.
Thank you.