Paul Libbrecht wrote:
I think this is related to the fact that you, here, don't get the
output message but the stacktrace. This should be changed in the jelly
file itself, presumably with an option like --stacktrace or
--no-stacktrace. Don't know which one should be the default.
I think as a scripting language, Jelly should output clean messages
first and foremost, and provide stack traces optionally, or to a
different (log?) stream
Paul
Le Lundi, 27 janv 2003, � 17:09 Europe/Berlin, Christian Sell a �crit :
apart from the strange (null, -1, -1) arguments,wasnt there a
consensus that the message below
org.apache.commons.jelly.JellyException: null:-1:-1: <null> Script
file wftest.jelly not found
at
org.apache.commons.jelly.util.CommandLineParser.invokeCommandLineJelly(
CommandLineParser.java:128)
at org.apache.commons.jelly.Jelly.main(Jelly.java:137)
should rather be something like
file.name:line:column: org.apache.commons.jelly.JellyException....
otherwise the purpose of being IDE digestable is again defeated..
Christian
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
