Users List
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile'
works?
My adversion to running 'mvn clean install' is just that I'd prefer
not to have to build and install something just to be able to examine
its dependencies.
This is merely a preference, right?
under various
, November 20, 2009 4:26 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
Brian --
Thanks for this. I did run the combo 'mvn compile dependency:tree' as you
mention below, and it works. What I'm taking away from
My adversion to running 'mvn clean install' is just that I'd prefer not to
have
to build and install something just to be able to examine its dependencies.
This is merely a preference, right?
under various 3rd party dependency scenarios. It seems backwards to me to have
to first build and
: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
Jamie --
Thanks for trying it out, and for the explanation. This makes sense in terms
of why things are happening, so that's nice.
I'm not familiar with the dependency plugin developers (are you one?), and
wonder
@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile'
works?
Jamie --
Thanks for trying it out, and for the explanation. This makes sense in
terms of why things are happening, so that's nice.
I'm not familiar with the dependency plugin developers
, November 19, 2009 3:00 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile'
works?
Jamie --
Thanks for trying it out, and for the explanation. This makes sense in
terms of why things are happening, so that's nice.
I'm
), you'll get the same error about not being
able to resolve dependencies.
Hope that helps.
Jamie.
-Original Message-
From: Jonathan Gold [mailto:jgold...@gmail.com]
Sent: Thursday, November 19, 2009 12:52 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail
.
Hope that helps.
Jamie.
-Original Message-
From: Jonathan Gold [mailto:jgold...@gmail.com]
Sent: Thursday, November 19, 2009 12:52 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
Brian --
Thanks for your help so
, 2009 3:00 PM
To: users@maven.apache.org
Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
Jamie --
Thanks for trying it out, and for the explanation. This makes sense in terms of
why things are happening, so that's nice.
I'm not familiar with the dependency plugin
Likely because dependency plugin has bugs, and I'm suspecting that your
issue is similar/related to this
http://jira.codehaus.org/browse/MDEP-204one already reported.
But it's odd that it doesn't fail for you at module mod_c, as build reactor
should have ordered mod_c to be built/processed before
Thanks for the response. In fact, I have all of my modules listed in depdendency
order in the parent pom, so it's quite odd indeed.
Thanks for the tip -- I voted for the bug, for what it's worth.
jon
On Wed, Nov 18, 2009 at 06:59:41PM +0100, Stevo Slavić wrote:
Likely because dependency plugin
You could try to install your project first, and after that run
dependency:tree.
Regards,
Stevo.
On Wed, Nov 18, 2009 at 7:05 PM, Jonathan Gold jgold...@gmail.com wrote:
Thanks for the response. In fact, I have all of my modules listed in
depdendency
order in the parent pom, so it's quite
AFAIK dependency tree does not run in the reactor. Is mod_d depending
on a SNAPSHOT version of mod_c? Do you have that version installed in
your local repo?
I have used dependency tree many time on a large mutli-module project so
I can attest that it does work in some form.
-Original
Jamie --
Thanks for the response. I don't have mod_d depending on a snapshot -- just on
the sibling module itself. Also, I'm not installing versions in the local repo
at the point I'm seeing this problem (and would rather not, actually, since it's
just for development anyway).
If mod_d was
This is not related. The dependency plugin has some issues resolving
things from the reactor and ranges in the following goals only:
copy
unpack
go-offline
resolve-plugins
All the other goals set @requiresDependencyResolution test which will
cause Maven to resolve all dependencies prior to the
15 matches
Mail list logo