You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nigel Magnay <ni...@gmail.com> on 2007/10/26 15:17:00 UTC
dependency:resolve and dependency:tree
Hello
I have a war project (actually, a cargo uberwar project), which I want to
analyse using dependency:resolve / dependency:tree (and maybe even through
site reporting) in order to find dependency conflicts.
However - the dependency plugin does not show the jar files that are a part
of the dependent war files - it is cut off at the jar level.
Is it possible to configure it to descend the dependency tree into WAR
artifacts as well? Without this my dependency list looks fine, but I have
WAR files with differing versions in them...
Nigel
Re: dependency:resolve and dependency:tree
Posted by Nigel Magnay <ni...@gmail.com>.
Hmm - ok. FWIW, I'm seeing 3.1 on dependency:resolve as well.
Yes - the dependencies of the WAR (which will be the same as those inside
it, if it's generated by maven). If I use cargo's merging (or I think just
the war plugin itself) to build a war file out of other war fragments,
merging them together, it's possible to get 2 versions of a dependency in
the output WEB-INF/lib. It'd be really nice to be able to find out that this
is happening in the convergence report or dependency analysis..
On 27/10/2007, Brian E. Fox <br...@reply.infinity.nu> wrote:
>
> It's possible that some other dependency has the 3.1 set. Use mvn -X to
> see the actual resolution, the tree mojo is still in progress.
>
> I don't understand your question about the war files. Are you expecting
> to see the dependencies inside the war or OF the war?
>
> -----Original Message-----
> From: Nigel Magnay [mailto:nigel.magnay@gmail.com]
> Sent: Friday, October 26, 2007 9:43 AM
> To: Maven Users List
> Subject: Re: dependency:resolve and dependency:tree
>
> .. and on a related note...
>
> When I do dependency:tree on a project that contains
>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate</artifactId>
> <version>3.2.4.ga</version>
> <type>jar</type>
> <scope>compile</scope>
> </dependency>
>
> In the hibernate pom in my repository, it says
> ...
> <dependency>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>2.1.1</version>
> </dependency>
> ...
> Why does dependency:tree show it as 3.1 ?!?!
>
> org.hibernate:hibernate:jar:3.2.4.ga:compile
> [INFO] net.sf.ehcache:ehcache:jar:1.2.3:compile
> [INFO] commons-logging:commons-logging:jar:1.1:compile
> [INFO] asm:asm-attrs:jar:1.5.3:compile
> [INFO] antlr:antlr:jar:2.7.6:compile
> [INFO] cglib:cglib:jar:2.1_3:compile
> [INFO] asm:asm:jar:1.5.3:compile
> [INFO] commons-collections:commons-collections:jar:3.1:compile
>
> Is this also the reason why my dependency convergence report looks OK,
> when
> really there's a mismatch ?
>
>
>
> On 26/10/2007, Nigel Magnay <ni...@gmail.com> wrote:
> >
> > Hello
> >
> > I have a war project (actually, a cargo uberwar project), which I want
> to
> > analyse using dependency:resolve / dependency:tree (and maybe even
> through
> > site reporting) in order to find dependency conflicts.
> >
> > However - the dependency plugin does not show the jar files that are a
> > part of the dependent war files - it is cut off at the jar level.
> >
> > Is it possible to configure it to descend the dependency tree into WAR
> > artifacts as well? Without this my dependency list looks fine, but I
> have
> > WAR files with differing versions in them...
> >
> > Nigel
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: dependency:resolve and dependency:tree
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
It's possible that some other dependency has the 3.1 set. Use mvn -X to
see the actual resolution, the tree mojo is still in progress.
I don't understand your question about the war files. Are you expecting
to see the dependencies inside the war or OF the war?
-----Original Message-----
From: Nigel Magnay [mailto:nigel.magnay@gmail.com]
Sent: Friday, October 26, 2007 9:43 AM
To: Maven Users List
Subject: Re: dependency:resolve and dependency:tree
.. and on a related note...
When I do dependency:tree on a project that contains
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.2.4.ga</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
In the hibernate pom in my repository, it says
...
<dependency>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>2.1.1</version>
</dependency>
...
Why does dependency:tree show it as 3.1 ?!?!
org.hibernate:hibernate:jar:3.2.4.ga:compile
[INFO] net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] commons-logging:commons-logging:jar:1.1:compile
[INFO] asm:asm-attrs:jar:1.5.3:compile
[INFO] antlr:antlr:jar:2.7.6:compile
[INFO] cglib:cglib:jar:2.1_3:compile
[INFO] asm:asm:jar:1.5.3:compile
[INFO] commons-collections:commons-collections:jar:3.1:compile
Is this also the reason why my dependency convergence report looks OK,
when
really there's a mismatch ?
On 26/10/2007, Nigel Magnay <ni...@gmail.com> wrote:
>
> Hello
>
> I have a war project (actually, a cargo uberwar project), which I want
to
> analyse using dependency:resolve / dependency:tree (and maybe even
through
> site reporting) in order to find dependency conflicts.
>
> However - the dependency plugin does not show the jar files that are a
> part of the dependent war files - it is cut off at the jar level.
>
> Is it possible to configure it to descend the dependency tree into WAR
> artifacts as well? Without this my dependency list looks fine, but I
have
> WAR files with differing versions in them...
>
> Nigel
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: dependency:resolve and dependency:tree
Posted by Nigel Magnay <ni...@gmail.com>.
.. and on a related note...
When I do dependency:tree on a project that contains
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate</artifactId>
<version>3.2.4.ga</version>
<type>jar</type>
<scope>compile</scope>
</dependency>
In the hibernate pom in my repository, it says
...
<dependency>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>2.1.1</version>
</dependency>
...
Why does dependency:tree show it as 3.1 ?!?!
org.hibernate:hibernate:jar:3.2.4.ga:compile
[INFO] net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] commons-logging:commons-logging:jar:1.1:compile
[INFO] asm:asm-attrs:jar:1.5.3:compile
[INFO] antlr:antlr:jar:2.7.6:compile
[INFO] cglib:cglib:jar:2.1_3:compile
[INFO] asm:asm:jar:1.5.3:compile
[INFO] commons-collections:commons-collections:jar:3.1:compile
Is this also the reason why my dependency convergence report looks OK, when
really there's a mismatch ?
On 26/10/2007, Nigel Magnay <ni...@gmail.com> wrote:
>
> Hello
>
> I have a war project (actually, a cargo uberwar project), which I want to
> analyse using dependency:resolve / dependency:tree (and maybe even through
> site reporting) in order to find dependency conflicts.
>
> However - the dependency plugin does not show the jar files that are a
> part of the dependent war files - it is cut off at the jar level.
>
> Is it possible to configure it to descend the dependency tree into WAR
> artifacts as well? Without this my dependency list looks fine, but I have
> WAR files with differing versions in them...
>
> Nigel
>
>