That works. Thanks.
Wayne Fay wrote:
You will want to use an excludes, something along the lines of:
acegi
acegi
1.0.1
compile
spring
spring
This is obviously not a proper dependency node, but you'll figure it
out from here I thin
You will want to use an excludes, something along the lines of:
acegi
acegi
1.0.1
compile
spring
spring
This is obviously not a proper dependency node, but you'll figure it
out from here I think.
Wayne
On 7/21/06, Denis McCarthy <
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 q
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
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 vi
