You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Wendy Smoak <ws...@gmail.com> on 2005/11/25 20:57:23 UTC

[m2] Transitive dependencies and relocation

If I declare a dependency on Spring 1.2.6 and a project that depends
on Spring 1.2.5...

      <dependency>
         <groupId>org.springframework</groupId>
         <artifactId>spring</artifactId>
         <version>1.2.6</version>
      </dependency>
      <dependency>
         <groupId>org.apache.shale</groupId>
         <artifactId>shale-spring</artifactId>
         <version>1.0.0-SNAPSHOT</version>
      </dependency>

where shale-spring depends on the 'old' groupId of springframework:

      <dependency>
         <groupId>springframework</groupId>
         <artifactId>spring</artifactId>
         <version>1.2.5</version>
      </dependency>

Then I get both Spring jars in WEB-INF/lib.

In this case, I'm in control of both build files, so I can fix it, but
that will not always be the case.  Shouldn't Maven be able to figure
out that springframework was relocated to org.springframework (or the
other way around) and deal with it?

Thanks,
--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] Transitive dependencies and relocation

Posted by Carlos Sanchez <ca...@apache.org>.
There's an issue in jira and I think has already been fixed in svn

On 11/25/05, Wendy Smoak <ws...@gmail.com> wrote:
> If I declare a dependency on Spring 1.2.6 and a project that depends
> on Spring 1.2.5...
>
>       <dependency>
>          <groupId>org.springframework</groupId>
>          <artifactId>spring</artifactId>
>          <version>1.2.6</version>
>       </dependency>
>       <dependency>
>          <groupId>org.apache.shale</groupId>
>          <artifactId>shale-spring</artifactId>
>          <version>1.0.0-SNAPSHOT</version>
>       </dependency>
>
> where shale-spring depends on the 'old' groupId of springframework:
>
>       <dependency>
>          <groupId>springframework</groupId>
>          <artifactId>spring</artifactId>
>          <version>1.2.5</version>
>       </dependency>
>
> Then I get both Spring jars in WEB-INF/lib.
>
> In this case, I'm in control of both build files, so I can fix it, but
> that will not always be the case.  Shouldn't Maven be able to figure
> out that springframework was relocated to org.springframework (or the
> other way around) and deal with it?
>
> Thanks,
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org