Amad Fida wrote:
Ben, I am starting to use acegi in myAcegi Security is pretty backward compatible with Spring. The only newer Spring features that Acegi Security currently uses is AspectJ support and EH-CACHE integration. Having said that, I recommend people use the latest official Spring release, particularly as it offers excellent backwards compatibility. We always develop with (and support use of) the latest official Spring release.
spring-richclient project, the first problem i ran
into was the different version of spring jars. Well I
know you Acegi is using version 1.1.3 but I am not
sure of versions used by spring-richclient as they
need to update the versions.txt. You guys use version
in file name and they keep version in version.txt.
I guess the question is which spring jars i should be
using?
Acegi Security's dependency JARs include the version number in their filenames, as we use Maven and that's just the way Maven operates. Personally I find it convenient having version numbers in the JAR filenames, especially given they are never put into CVS (or Ant scripts), which is the main argument against.
I'm not sure which Spring JAR version(s) that Spring Rich is currently using. They were checked in on 27 November and their manifest file suggests version 1.1.3-dev. I would use the Spring Rich version in preference to the Acegi Security version, given the former uses many of Spring's newer features and the latter is widely compatible with different Spring versions anyway.
Ben
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
