commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Sell <christian.s...@netcologne.de>
Subject Re: [jelly] script error messages
Date Wed, 29 Jan 2003 00:23:21 GMT
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:commons-user-unsubscribe@jakarta.apache.org>
>> For additional commands, e-mail:  
>> <mailto:commons-user-help@jakarta.apache.org>
>>
> 
> 
> -- 
> To unsubscribe, e-mail:   
> <mailto:commons-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:commons-user-help@jakarta.apache.org>
> 
> 



Mime
View raw message