May 21, 2008 3:11 PM
To: Maven Developers List
Subject: Re: Resolving parent poms in the dependency tree
Just as an example, if I run "mvn dependency:tree" on the maven jar
plugin, I
currently see the dependency on maven-project.
[INFO]
org.apache.maven.plugins:maven-jar-plu
is used, or to find out what parents
a project uses? (or both?)
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 3:11 PM
To: Maven Developers List
Subject: Re: Resolving parent poms in the dependency tree
Just as an example, if I run "mvn depe
x27;t actually do anything since it will
already
be resolved. Can you provide an example of what you expect the output
to
look like?
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21,
2008 2:31 PM
To: Maven Developers List
Subject: Re: Resolving par
ms, I don't see what
this adds, nor how to show it any more as a tree.
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 2:44 PM
To: Maven Developers List
Subject: Re: Resolving parent poms in the dependency tree
I just want the parent poms to
44 PM
To: Maven Developers List
Subject: Re: Resolving parent poms in the dependency tree
I just want the parent poms to print in the output. Both in the tree
view and
in the list generated by resolve.
So you would include things like:
org.apache.maven.plugins:maven-plugins:pom:12-SNAPSHOT:co
will already
be resolved. Can you provide an example of what you expect the output to
look like?
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 2:31 PM
To: Maven Developers List
Subject: Re: Resolving parent poms in the dependency tree
If the
bject: Re: Resolving parent poms in the dependency tree
If they are not dependencies of the project, then what are they? They
do have
some relation to the project because they are needed in order to build,
so I'm
just wondering where they fit in. Would it be reasonable to add a
paramet
If they are not dependencies of the project, then what are they? They do have
some relation to the project because they are needed in order to build, so I'm
just wondering where they fit in. Would it be reasonable to add a parameter to
the dependency plugin's resolve and tree goals to also inc
Both of those goals require Maven to do the dependency resolution, which
means the parent poms will already be resolved at that point. Strictly
speaking, the parents are not dependencies of the projects as we are
looking only at binary artifacts. Getting the parent poms is out of the
scope of those
