Mick,
I'm not using Spring and Acegi, so this might not work, but perhaps
try adding an <excludes> node on the Acegi dependency to exclude
Spring, and then add the Spring dependency by itself.
If this doesn't work, post your pom back to the list and we'll try to
help debug it some more...
Wayne
On 10/10/06, Mick Knutson <[EMAIL PROTECTED]> wrote:
Is anyone else using spring 2.0 and acegi 1.0.2????
It seems acegi 1.0.2 is requiring spring 1.2.7 and adds 1.2.7 and 2.0 into
my ear.
Is this an issue with the spring libs I imported?
On 9/18/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> On 9/18/06, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> > I am trying to use this:
> ... {spring dependencies} ...
> > But my war seems to be getting 1.2.7 and 2.0-rc3 jars
> > Why?
>
> Did you upgrade this app to Spring 2? If so, did you 'mvn clean'
> after changing the dependency versions? The old ones may have been
> left in WEB-INF/lib under 'target'.
>
> If that's not it, run
> mvn package -X > output.txt
>
> and take a look at the output, which will include an indented tree
> view of dependencies. You'll be able to see where each dependency is
> coming from, and exclude the ones you don't want.
>
> You can get two versions of the same library if the groupId has
> changed without being "relocated" in the repository. (Didn't Spring
> change from 'springframework' to 'org.springframework'?) Maven has no
> way of knowing they are the 'same'.
>
> HTH,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Thanks
DJ MICK
http://www.djmick.com
http://www.myspace.com/mickknutson
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
