From what I recall, nobody has yet updated dependency:tree to query
aether's graph directly rather than go through the emulation of 2.x's API
for examining the dependency tree. When I last chatted on this with
Benjamin, he left me with the distinct impression that I should not rely on
the output
is Confidential. We only send and receive email on the basis
of the terms set out at www.ericsson.com/email_disclaimer
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, June 04, 2012 4:10 PM
To: Maven Users List
Subject: Re: maven dependency plugin
send and receive email on the
basis of the terms set out at www.ericsson.com/email_disclaimer
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Monday, June 04, 2012 4:10 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3
at www.ericsson.com/email_disclaimer
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Monday, June 04, 2012 5:24 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3
Please don't hijack someone
Update !
Creating a jira for this issue, providing the same example pom,
http://jira.codehaus.org/secure/attachment/60149/pom.xml
when I tried to reproduce on a linux box, with the latest maven 3.0.4
1) do a mvn package
2) then do a mvn
[WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
[WARNING] Missing POM for
net.dahanne.gallery:commons-gallery:jar:2.1.0-SNAPSHOT
even though those 2 artifacts are existing in my local repo.
Have you looked at the content of those pom files to ensure they
aren't corrupted?
Wayne
Hi Wayne,
you are right, running the purge corrupted my local repo in a way :
$ ls ~/.m2/repository/javax/servlet/servlet-api/2.5/
_maven.repositories servlet-api-2.5.jar
servlet-api-2.5.jar.lastUpdated servlet-api-2.5.jar.sha1
and if I run mvn clean install just after , everything
You need to make a test case so we can reproduce it. It's impossible to tell
whether it's you, your environment, the dependency plugin or Maven itself from
looking at the textual output of the build.
On Jun 3, 2012, at 11:42 AM, Anthony Dahanne wrote:
Hello all,
sorry to bump ... :-(
but
