You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bill Simons (JIRA)" <ji...@codehaus.org> on 2007/11/19 19:53:41 UTC
[jira] Created: (MEV-556) jaxws jar is incorrect
jaxws jar is incorrect
----------------------
Key: MEV-556
URL: http://jira.codehaus.org/browse/MEV-556
Project: Maven Evangelism
Issue Type: Bug
Components: Problem with Jar
Reporter: Bill Simons
The jar in the primary maven repository located at http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/jaxws-api-2.1.jar has the same groupId, artifactId and version as the jar located in the java.net repository at http://download.java.net/maven/1/javax.xml.ws/jars/jaxws-api-2.1.jar. However, the jars are different. The jar located in the java.net repository is correct and contains all the necessary classes. The problem is that poms resolve the main maven repo first and so we get the wrong jar.
I'm looking for a workaround, but in the meantime, it would be great if you could get the correct jar deployed.
--
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
[jira] Closed: (MEV-556) jaxws jar is incorrect
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlos Sanchez closed MEV-556.
------------------------------
Assignee: Carlos Sanchez
Resolution: Duplicate
> jaxws jar is incorrect
> ----------------------
>
> Key: MEV-556
> URL: http://jira.codehaus.org/browse/MEV-556
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Problem with Jar
> Reporter: Bill Simons
> Assignee: Carlos Sanchez
>
> The jar in the primary maven repository located at http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/jaxws-api-2.1.jar has the same groupId, artifactId and version as the jar located in the java.net repository at http://download.java.net/maven/1/javax.xml.ws/jars/jaxws-api-2.1.jar. However, the jars are different. The jar located in the java.net repository is correct and contains all the necessary classes. The problem is that poms resolve the main maven repo first and so we get the wrong jar.
> I'm looking for a workaround, but in the meantime, it would be great if you could get the correct jar deployed.
--
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