[
http://jira.codehaus.org/browse/MNG-4954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Bricon updated MNG-4954:
-----------------------------
Description:
I stumbled upon a weird issue, where failing to resolve a transitive dependency
marks all the other ones as missing too.
In the attached project,
org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
depends on com.sun.xml.ws:jaxws-rt:pom:2.1.7 which can't be resolved since the
legacy layout of java.net is no longer supported.
So far so good. Problem is, *ALL* other dependencies, which actually exist in
my local repo, seem to be missing too.
{noformat}
[ERROR] Failed to execute goal on project project: Could not resolve dependencie
s for project my.group:project:jar:1.0-SNAPSHOT: Failed to collect dependencies
for [org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incu
bating (compile), junit:junit:jar:4.8.1 (test), org.dbunit:dbunit:jar:2.4.8 (tes
t), hsqldb:hsqldb:jar:1.8.0.7 (test), commons-lang:commons-lang:jar:2.3 (compile
), commons-io:commons-io:jar:1.4 (compile)]: Failed to read artifact descriptor
for com.sun.xml.ws:jaxws-rt:jar:2.1.7: Could not transfer artifact com.sun.xml.w
s:jaxws-rt:pom:2.1.7 from/to maven-repository.dev.java.net (http://download.java
.net/maven/1/): No connector available to access repository maven-repository.dev
.java.net (http://download.java.net/maven/1/) of type legacy using the available
factories WagonRepositoryConnectorFactory -> [Help 1]
{noformat}
In m2eclipse, it's even more confusing !unresolved-deps.jpg!
Expected behavior : resolved dependencies shouldn't be flagged as missing.
Expected message would rather look like :
{noformat}
[ERROR] Failed to execute goal on project project: Could not resolve
dependencies for project foo.bar:project:jar:1.0-SNAPSHOT:
Failed to collect dependencies for
[org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
(compile)]:
Failed to read artifact descriptor for com.sun.xml.ws:jaxws-rt:jar:2.1.7:
Could not transfer artifact com.sun.xml.ws:jaxws-rt:pom:2.1.7 from/to
maven-repository.dev.java.net (http://download.java.net/maven/1/):
No connector available to access repository maven-repository.dev.java.net
(http://download.java.net/maven/1/)
of type legacy using the available factories WagonRepositoryConnectorFactory ->
[Help 1]
{noformat}
was:
I stumbled upon a weird issue, where failing to resolve a transitive dependency
marks all the other ones as missing too.
In the attached project,
org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
depends on com.sun.xml.ws:jaxws-rt:pom:2.1.7 which can't be resolved since the
legacy layout of java.net is no longer supported.
So far so good. Problem is, *ALL* other dependencies, which actually exist in
my local repo, seem to be missing too.
{noformat}
[ERROR] Failed to execute goal on project project: Could not resolve dependencie
s for project my.group:project:jar:1.0-SNAPSHOT: Failed to collect dependencies
for [org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incu
bating (compile), junit:junit:jar:4.8.1 (test), org.dbunit:dbunit:jar:2.4.8 (tes
t), hsqldb:hsqldb:jar:1.8.0.7 (test), commons-lang:commons-lang:jar:2.3 (compile
), commons-io:commons-io:jar:1.4 (compile)]: Failed to read artifact descriptor
for com.sun.xml.ws:jaxws-rt:jar:2.1.7: Could not transfer artifact com.sun.xml.w
s:jaxws-rt:pom:2.1.7 from/to maven-repository.dev.java.net (http://download.java
.net/maven/1/): No connector available to access repository maven-repository.dev
.java.net (http://download.java.net/maven/1/) of type legacy using the available
factories WagonRepositoryConnectorFactory -> [Help 1]
{noformat}
In m2eclipse, it's even more confusing !unresolved-deps.jpg!
Expected behavior : resolved dependencies shouldn't be flagged as missing.
Expected message would rather look like :
{noformat}
[ERROR] Failed to execute goal on project project: Could not resolve
dependencies for project foo.bar:project:jar:1.0-SNAPSHOT: Failed to collect
dependencies for
[org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
(compile)]: Failed to read artifact descriptor for
com.sun.xml.ws:jaxws-rt:jar:2.1.7: Could not transfer artifact
com.sun.xml.ws:jaxws-rt:pom:2.1.7 from/to maven-repository.dev.java.net
(http://download.java.net/maven/1/): No connector available to access
repository maven-repository.dev.java.net (http://download.java.net/maven/1/) of
type legacy using the available factories WagonRepositoryConnectorFactory ->
[Help 1]
{noformat}
> Confusing error report when transitive dependencies can't be resovled
> ---------------------------------------------------------------------
>
> Key: MNG-4954
> URL: http://jira.codehaus.org/browse/MNG-4954
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0.1
> Environment: Apache Maven 3.0.1 (r1038046; 2010-11-23 11:58:32+0100)
> Java version: 1.6.0_22
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
> Reporter: Fred Bricon
> Priority: Minor
> Attachments: pom.xml, unresolved-deps.jpg
>
>
> I stumbled upon a weird issue, where failing to resolve a transitive
> dependency marks all the other ones as missing too.
> In the attached project,
> org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
>
> depends on com.sun.xml.ws:jaxws-rt:pom:2.1.7 which can't be resolved since
> the legacy layout of java.net is no longer supported.
> So far so good. Problem is, *ALL* other dependencies, which actually exist in
> my local repo, seem to be missing too.
> {noformat}
> [ERROR] Failed to execute goal on project project: Could not resolve
> dependencie
> s for project my.group:project:jar:1.0-SNAPSHOT: Failed to collect
> dependencies
> for
> [org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incu
> bating (compile), junit:junit:jar:4.8.1 (test), org.dbunit:dbunit:jar:2.4.8
> (tes
> t), hsqldb:hsqldb:jar:1.8.0.7 (test), commons-lang:commons-lang:jar:2.3
> (compile
> ), commons-io:commons-io:jar:1.4 (compile)]: Failed to read artifact
> descriptor
> for com.sun.xml.ws:jaxws-rt:jar:2.1.7: Could not transfer artifact
> com.sun.xml.w
> s:jaxws-rt:pom:2.1.7 from/to maven-repository.dev.java.net
> (http://download.java
> .net/maven/1/): No connector available to access repository
> maven-repository.dev
> .java.net (http://download.java.net/maven/1/) of type legacy using the
> available
> factories WagonRepositoryConnectorFactory -> [Help 1]
> {noformat}
> In m2eclipse, it's even more confusing !unresolved-deps.jpg!
> Expected behavior : resolved dependencies shouldn't be flagged as missing.
> Expected message would rather look like :
> {noformat}
> [ERROR] Failed to execute goal on project project: Could not resolve
> dependencies for project foo.bar:project:jar:1.0-SNAPSHOT:
> Failed to collect dependencies for
> [org.apache.chemistry.opencmis:chemistry-opencmis-client-impl:jar:0.1.0-incubating
> (compile)]:
> Failed to read artifact descriptor for com.sun.xml.ws:jaxws-rt:jar:2.1.7:
> Could not transfer artifact com.sun.xml.ws:jaxws-rt:pom:2.1.7 from/to
> maven-repository.dev.java.net (http://download.java.net/maven/1/):
> No connector available to access repository maven-repository.dev.java.net
> (http://download.java.net/maven/1/)
> of type legacy using the available factories WagonRepositoryConnectorFactory
> -> [Help 1]
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
