commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Zoller <g...@codaware.com>
Subject Re: Bugs in Jelly?
Date Wed, 07 May 2003 15:48:24 GMT
That may be the case, but nonetheless the appearance of errors
(vs warnings) is very disconcerting when considering using tools
in a production environment.  I am having serious problems getting
maven and xdoclet struts tags to generate and the log file show
copious jelly errors.  So before I go annoying people on the xdoclet
list I have to ensure that jelly is in fact ok.   The best way to do
that is to have some way to dump out the script jelly is trying to
parse thereby proving that the fault is not jelly's but the scripts
(this would also help me identify bad scripts!).

So, to that end, I'm asking the community if there's a way to dump
out a Script object as a string?  toString() isn't mandated in
Script.java and some descendents implement one, others dont.
Right now the output is not very useful/helpful.

Thanks
Greg

dion@multitask.com.au wrote:

>Greg,
>fyi, every time I've seen the sort of errors listed below there has been 
>no problem with Maven, just some overly zealous messages on jelly's part.
>--
>dIon Gillard, Multitask Consulting
>Blog:      http://www.freeroller.net/page/dion/Weblog
>Work:      http://www.multitask.com.au
>
>
>Greg Zoller <greg@codaware.com> wrote on 06/05/2003 08:38:35 PM:
>
>  
>
>>Hello...
>>
>>I'm getting a lot of errors (including some exceptions) when running 
>>maven.  According to maven.log these are coming out of jelly tasks.
>>
>>Before trying to trace cause to either jelly, maven, or the plugin
>>developers a HUGE problem I'm having is not being able to tell what
>>is being parsed.  In Jelly the Script interface doesn't define a 
>>toString() method and so printing out a script object doesn't give me 
>>anything helpful.
>>
>>Does anyone have some suggestings/best practices to help me trace where 
>>these errors might be originating?
>>
>>Thanks
>>Greg
>>
>>fyi, here's a sample of a "naked" (no target) maven.log file.
>>If I do something more complex I get a lot more errors and some
>>exceptions.  I want to be able to trace where these are coming from.
>>
>>2003-05-06 03:37:58,479 INFO  org.apache.maven.plugin.PluginManager - 
>>Initializing Plugins!
>>2003-05-06 03:37:58,534 INFO  org.apache.maven.plugin.PluginManager - 
>>Processing Plugin: maven-sea-plugin-1.0
>>2003-05-06 03:37:58,697 INFO  org.apache.maven.plugin.PluginManager - 
>>Processing Plugin: maven-deploy-plugin-1.1
>>2003-05-06 03:37:58,738 INFO  org.apache.maven.plugin.PluginManager - 
>>Processing Plugin: maven-vdoclet-plugin-1.0
>>2003-05-06 03:37:58,744 INFO  org.apache.maven.plugin.PluginManager - 
>>Processing Plugin: maven-plexus-plugin-0.2
>>2003-05-06 03:37:58,775 INFO  org.apache.maven.plugin.PluginManager - 
>>Processing Plugin: maven-castor-plugin-1.0
>>2003-05-06 03:37:58,855 INFO  org.apache.maven.plugin.PluginManager - 
>>Finished initializing Plugins!
>>2003-05-06 03:38:00,936 ERROR org.apache.commons.jelly.tags.ant.AntTag - 
>>    
>>
>
>  
>
>>Class org.apache.commons.jelly.tags.core.IfTag doesn't support the 
>>nested "available" element.
>>2003-05-06 03:38:00,960 ERROR org.apache.commons.jelly.tags.ant.AntTag - 
>>    
>>
>
>  
>
>>Class com.werken.werkz.jelly.ProjectTag doesn't support the nested 
>>"path" element.
>>2003-05-06 03:38:01,037 ERROR org.apache.commons.jelly.tags.ant.AntTag - 
>>    
>>
>
>  
>
>>Class org.apache.commons.jelly.tags.core.IfTag doesn't support the 
>>nested "path" element.
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>  
>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message