jar versioning problem

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

Re: jar versioning problem

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

Re: jar versioning problem

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

Re: jar versioning problem

You will want to use an excludes, something along the lines of: dependency groupIdacegi artifactIdacegi version1.0.1/version scopecompile/scope exclusions exclusion groupIdspring artifactIdspring /exclusion This is obviously not a

Re: jar versioning problem

That works. Thanks. Wayne Fay wrote: You will want to use an excludes, something along the lines of: dependency groupIdacegi artifactIdacegi version1.0.1/version scopecompile/scope exclusions exclusion groupIdspring artifactIdspring