Hi Amit,
You can use dependency exclusions [1,2].
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
<version>2.0.6</version>
</dependency>
<dependency>
<groupId>org.acegisecurity</groupId>
<artifactId>acegi-security</artifactId>
<version>1.0.4</version>
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
</exclusion>
</exclusions>
</dependency>
Regards,
Jonas
[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
[2]
http://www.sonatype.com/book/pom-relationships.html#project_relationships
On Sat, 2007-06-23 at 11:31 -0400, Amit Prahesh wrote:
> Hello,
>
> I'm using the Spring Framework in my web application, having declared
> it in my pom's dependecies like this:
>
> <dependency>
> <groupId>org.springframework</groupId>
> <artifactId>spring</artifactId>
> <version>2.0.6</version>
> </dependency>
>
> Everything's fine. When I issue a mvn package things go smoothly and
> everything goes as advertised. Now, I wanted to add Acegi Security to
> the mix, so I added this as yet another dependency:
>
> <dependency>
> <groupId>org.acegisecurity</groupId>
> <artifactId>acegi-security</artifactId>
> <version>1.0.4</version>
> </dependency>
>
> It seems that this specific version (which I gather is the latest one)
> depends on Spring version 2.0.4. Now, when I package my app it will
> include some jars for this version, so I end up packaging Spring
> Framework 2.0.6 AND 2.0.4.
>
> My question is this: is there a way for me to tell Acegi not to worry
> about the 'old' Spring version? Is this something the Acegi 'packager'
> should fix?
>
> Thanks a lot,
> Amit.
>
> ---------------------------------------------------------------------
> 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]
