[
http://jira.codehaus.org/browse/MEV-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MEV-573.
------------------------------
Assignee: Carlos Sanchez
Resolution: Fixed
as you were already told in the Maven list.
We can' t answer for what's done in the java.net repo either
> Inconsistent pom for jaxws-api 2.1
> ----------------------------------
>
> Key: MEV-573
> URL: http://jira.codehaus.org/browse/MEV-573
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Incomplete POM
> Reporter: Raymond Feng
> Assignee: Carlos Sanchez
>
> Our build has a dependency on javax.xml.ws:jaxws-api:2.1. And we have the
> java.net configured as a maven repo in our pom.xml. The build fails randomly
> because the same artifact is available at [2] but it has a different pom as
> [1]. A bunch of transitive dependencies are missing in [2], such as jsr-181.
> If it happens that [2] is downloaded by mvn, then our build will fail.
> [1] http://download.java.net/maven/1/javax.xml.ws/poms/jaxws-api-2.1.pom
> [2]
> http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/jaxws-api-2.1.pom
> Is this a bug in [2]?
--
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
