The only "override" mecanism is the "nearer" dependency resolution. I
discourage using the spring(full) jar as you will get such conflicts. Make a
dependency on a top level spring-xxx-2.0.2 that will import other necessary
spring artifacts with correct version.
For unexpected artifact from acegi, use exclusions.

Acegi POM should refer to spring-remoting dependency as optional, so you may
post on acegi forum about this.

2007/1/19, Peter Mihalik <[EMAIL PROTECTED]>:

sure, i know that. but my project has a dependency on spring but does
not have a dependency on spring-remoting which acegi has
so i get a app containing spring-2.0.2 jar and some
spring-something-1.2.8 jars
i know about 2 options to resolve this:
1/ exclude the acegi dependencies and everything will be ok, because of
the spring dependency which covers all the acegi ones
2/ remove my spring dep and add some spring-all_the_things_i_need and
spring_all_the_things_acegi_needs deps and i will get only v. 2.0.2
spring jars
so my questions are:
is there a way to say maven that spring.jar covers all the
spring-something.jar s
or is there a way to override the version of acegi spring dependencies?

nicolas de loof wrote:
> Maven use a dependency conflit resolution based on "nearer"
> dependencies :
>
> if your project depends on acegi, that depends on spring 1.2.8,
> "1.2.8" is a
> "second level" dependency.
> if your project also set dependency on spring 2.0.2, "2.0.2" is a 'first
> level" dependency and will be used.
>
> Nico.
>
> 2007/1/19, Peter Mihalik <[EMAIL PROTECTED]>:
>>
>> hi, how can i override the acegi-security dependency on spring 1.2.8 to
>> a higher value, say 2.0.2?
>>
>> ---------------------------------------------------------------------
>> 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]


Reply via email to