It's stable as in its tested every which way. The only reason 0.4.0 is
carrying a beta tag is that I'm planning on adding a few operations,
and there's a remote possibility that some of the existing signatures
will change. I fully recommend every T5.2 user moving to 0.4.0 as soon
as possible.
Kall
Wow... Good job...
I can wait for the stable version :)
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-0-released-tp4459174p4474814.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
On Mon, Jun 6, 2011 at 6:33 PM, Kalle Korhonen
wrote:
> You've spoken and we aim to please! In tapestry-security 0.4.0 we did
> away with the shiro.ini and allowed configuring security
> Tapestry-style with all-in-Java contributions. The release finally
> combines all features from separate Shiro
You've spoken and we aim to please! In tapestry-security 0.4.0 we did
away with the shiro.ini and allowed configuring security
Tapestry-style with all-in-Java contributions. The release finally
combines all features from separate Shiro integrations (original
tapestry-security by Kalle Korhonen) and
