On May 10, 2010, at 1:39 PM, akochnev [via Tapestry Developers] wrote:
> Pierce,
> I just committed the changes to tapestry-spring-security to support
> spring-security 3.0.2 (and spring 3.0.2) and work w/ the latest T5.2
> snapshots . The changes are in the T-s-s SVN trunk since yesterday. The
> rewrite of T-s-s is exactly the reason for my questions on this topic.
>
> I haven't removed the extra private fields that the old code used to
> create, but you're right - they're probably expendable.
Oh, cool. Doing a source compare....
Yeah, you mostly replicated what I did.
The pom.xml checked in is still out of date. I made the following changes:
1. I updated the various version numbers in the properties.
2. I pointed the repositories at the EBR stuff mentioned on spring
source.
Hey! It worked!
Are you going to put a 3.0.0-SNAPSHOT up?
Pierce
--
View this message in context:
http://tapestry-developers.221625.n2.nabble.com/T5-2-ClassTransformation-why-deprecate-throw-an-exception-tp5028206p5033289.html
Sent from the Tapestry Developers mailing list archive at Nabble.com.
