Matt Raible wrote:
Acegi 1.0 was compiled against Spring 2.0, so there are some known
issues with the release. I'd suggest using Acegi 1.0.1 instead.
Matt
On 7/21/06, Denis McCarthy <[EMAIL PROTECTED]> wrote:
Hi,
I'm in the process of trying to get a project going with maven. The
project in question uses spring 2.0 and acegi security 1.0 (The latest
major versions of both projects). I was getting NoSuchMethodErrors when
running my tests. I noticed that in my eclipse classpath (which I
generated via maven) that both spring 1.2.7 and 2.0 were on the
classpath - obviously the source of the problem.
I also noticed that acegi had a dependency on spring 1.2.7. Is there
some way to explicitly exclude the 1.2.7 spring dependency that is being
dragged in by acegi (spring is backwards-compatible so acegi 1.0 will
work fine with spring 2)?
Thanks
Denis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Sorry, I should have been more explicit - I am using 1.0.1. The pom for
1.0.1 states an explicit dependency on 1.2.7 (which of course is fair
enough as spring 2.0 is not officially released yet). I just want to get
maven not to put this version of spring on the classpath in favour of
using 2.0-m4 (the latest version of spring on ibiblio with a pom)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
