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:compile
Brian E. Fox wrote:
Adding it to resolve doesn'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 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
parameter to
the dependency plugin's resolve and tree goals to also include the
parent poms?
Brian E. Fox wrote:
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 goals IMO.
-----Original Message-----
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 21, 2008 12:43 PM
To: Maven Developers List
Subject: Resolving parent poms in the dependency tree
I noticed that the dependency plugin currently does not include parent
poms when
generating the dependency tree (MDEP-167) or when calling
dependency:resolve.
Is the exclusion of the parent poms by design or is this something
that
just
hasn't been implemented yet? I would like to have a way to print out
all the
dependencies of my project (including poms, plugins, etc.) but
currently
I think
the only way to do this is to start with a clean repository, and then
look at
the contents after a build was run.
Long term, what is the best way to handle this? I didn't see any
current way in
the maven artifact resolution API to get a list of dependencies that
include
parent poms. Does it make sense to add something like this?
Thanks!
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
