If the agent is started with an invalid project name, it just outputs NullPointerExceptions and the software won't come up. Also, the error message doesn't really suggest the root cause at first sight.
It would be useful to check if the given directory is present before doing anything and automatically create it if not; maybe this could be enabled/disabled in the Jenson.properties. This way, at least the software comes up and manages to output some data; the user would still realize something is wrong because he can see the folder name isn't as he expected.
I came across this when trying to run instrumented software across several machines, after distributing Jensor to each. It's not really a big issue for me to include creating the project folder structure in that distribution, but I did get confused by it several times.
Log in to post a comment.