In theory Spring is guaranteeing that 2.0 is backwards compatible, so if it works on 1.2.x it'll work on 2.0.
In practice we could create a maven 2 profile setting the 2.0 dependencies and setting up continuous integration to build the default (1.2.x) and the profile too (2.x) On 5/31/06, Scott McCrory <[EMAIL PROTECTED]> wrote: > Carlos Sanchez wrote: > >> Sorry it wasn't spotted earlier. Perhaps we should change the Spring > >> maven dependency back to 1.2.8 to detect this kind of thing? > >> > > > > That's what i suggested some time ago. In fact for now only 1.2.7 is in > > ibiblio. > > > > > > Wouldn't that subsequently mean that Spring 2.x could surprise us? In > more general terms, how do we maximize compatibility testing with all > the major versions of Spring, the JDKs, app servers, etc.? > > Scott > > > _______________________________________________ > Home: http://acegisecurity.org > Acegisecurity-developer mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
