I was waiting to hear from one of the original developers (Robin) after he gets a chance to take a look at my changes before deciding what to do / when to release stuff. I think that all changes w/o the ClassTransformation fixes might make a nice Spring 3 + T5.1 compatible release, whereas the ones w/ the ClassTransormation changes would make a nice Spring 3 + T5.2 bundle.
Anyway, it's good to hear that it works for you. I can't say I've grokked the whole codebase yet; the migration (w/ the exception of ClassTransformation) was mostly an exercise in tracking down the newly repackaged & renamed classes from Spring Security 2 to S-S 3. Thus, I was concerned that I might have missed something un-obvious. Do you want to send me a patch (or just the POM file) w/ the updated pom so that I don't have to duplicate your effort ? Regards, Alex Kotchnev On Mon, May 10, 2010 at 6:09 PM, Pierce Wetter <[email protected]> wrote: > > > 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. >
