commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark R. Diggory" <>
Subject Re: [jelly] Stable release?
Date Fri, 06 Dec 2002 15:57:06 GMT

James Strachan wrote:
> From: "Mark R. Diggory" <>
>>I'm curious what is currently the most stable release of Jelly? I
>>checked out the cvs tree and tries to build it, but it seems to break on
>>certain dependencies.
> It shouldn't do. Are you using Maven to build it? What problems did you
> find - it should all just work.


cannot resolve symbol
     [javac] symbol  : class ConstructorUtils
     [javac] location: package beanutils
     [javac] import org.apache.commons.beanutils.ConstructorUtils;
     [javac]                                     ^

cannot resolve symbol
     [javac] symbol  : variable ConstructorUtils
     [javac] location: class org.apache.commons.jelly.tags.core.NewTag
     [javac]             object = 
     [javac]                      ^
     [javac] 2 errors

file:/root/CVS_ROOT/jakarta-commons-sandbox/jelly/build.xml:34: Compile 
failed; see the compiler error output for details.

>>I'd like to begin experimenting with Jelly as a
>>Mathematical Simulation tool, not neccessarily as a developer, so I'd
>>like a pretty stable release thats going to not be too buggy.
> Its pretty stable - its been used in various projects such as Maven for
> quite some time. Though we do really need to get a release out soon so folks
> can depend on a formal release. Until now you could depend on a snapshot
> build from here...

This is helpfull, but there are a great number of versions (nightly 
builds?, beta N's, dev branchs) which is the best to use?

For my experience working with other jakarta commons projects, its often 
hard to judge what the best release (formal or informal) to use is.

I definitly agree with the release thread going on now. For Jelly to be 
of use to the common user, there needs to be stable release points they 
can reley on. If their own work is based on the bleeding edge of the 
development branch it will create much suffering for them. This is 
because the HEAD branch cycles between states of stablity/unstability as 
development progresses. Depending on when they checkout the cvs, they 
could be grabbing from anywhere in cycle.

Another question, do you have a current timeline for releasing 1.0?

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message