Re: transient dependency conflict

[Mert Çalışkan]

maven will go for the "sequential first at the same distance".
so if  you have declared B as a dependency above C, you will get D:1.0 in
your classpath (whichever that you're using by specifying the scope).
use the dependencyManagement tag for handling transitive dependencies more
reasonably.

Mert.

On Tue, Mar 30, 2010 at 1:12 AM, WDS  wrote:

> Given the following project hierarchy:
>   D-1.0   D-2.0
>\  /
> B   C
>  \  /
>   A
>
> 'A' depends on 'B' and 'C', both of which depend on different versions of
> 'D'.
>
> When 'A' is built as an executable .jar with all dependencies on the
> CLASSPATH, won't there be an issue with 2 different versions of 'D'?
>
> What would be the best way to avoid these issues via project
> re-arrangement or otherwise?
>
> -wds
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Is It necessary that a POM with modules should have packaging as "pom"

[Mert Çalışkan]

yes,

see
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Aggregation

On Wed, Mar 17, 2010 at 3:02 PM, amaresh mourya wrote:

> Hi All,
>
> Question is asked in subject.
>
> Thanks,
> Amaresh
>

About maven 2.0.x and 2.2.x branches

[Mert Çalışkan]

Hi,

I looked around but couldn't find a good resource about the differences on
maven 2.0.x and 2.2.x branches.
What are the differences between those. I know that 2.2.x requires jdk1.5 at
least. is it the only differences?
pre jdk 1.5 & post jdk 1.5 branching?

Thanks,

Mert.