Spindle build 3.1.7 released

[Geoff Longman <gl...@gmail.com>]

Fixes a classpath problem. User's are not affected unless thier
projects use Enums from the commons-lang-1.0.jar

more info!

http://www.jroller.com/page/glongman/20050223#spindle_3_1_17_released

Geoff

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

Re: How stable is Tapestry 3.1 alpha?

[Erik Hatcher <er...@ehatchersolutions.com>]

I recommend using 3.0.  3.1 is early alpha and things will improve and 
evolve... and eventually there will be documentation detailing how to 
migrate from 3.0 to 3.1 making life much easier.

	Erik

On Feb 23, 2005, at 4:26 AM, Rosdi Kasim wrote:

>
> I just noticed that Tapestry 3.1 alpha has just been released.
>
> We currently have a projects that should be delivered in a month time, 
> I am tempted to implement it in Tapestry 3.1 because of the 
> improvement promised in the release (among others are like friendly 
> url, simplified component parameters, DTD specs, etc..).
>
> So should I wait and live with what I have now (Tapestry 3.0 is great! 
> I don't to sound like ungrateful though hehe), or is 3.1 stable enough 
> (for the brave soul, that is)?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


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

How stable is Tapestry 3.1 alpha?

[Rosdi Kasim <ro...@onepixel.com.my>]

I just noticed that Tapestry 3.1 alpha has just been released.

We currently have a projects that should be delivered in a month time, I 
am tempted to implement it in Tapestry 3.1 because of the improvement 
promised in the release (among others are like friendly url, simplified 
component parameters, DTD specs, etc..).

So should I wait and live with what I have now (Tapestry 3.0 is great! I 
don't to sound like ungrateful though hehe), or is 3.1 stable enough 
(for the brave soul, that is)?

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