[
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87337
]
Dan Tran commented on MEV-498:
------------------------------
jaxws-maven-plugin is in an odd situation where most of its dependencies are in
java.net maven1 repo. One of the dependency (jaxws-api) happen to be at repo1
as well.
Since repo1 is primary repo, its jaxws-api is picked up first and therefore
jaxws-maven-plugin is unusable.
Tell me what is correct action for this? Have java.net to pump up its release
number which I dont think it wil be available until 2.2.
Question, why does repo1 have a deployment of jaxws-2.1 way before it is
official released?
> javax.xml.ws:jaxws-api:2.1 is bad
> ---------------------------------
>
> Key: MEV-498
> URL: http://jira.codehaus.org/browse/MEV-498
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Dan Tran
>
> Sun just released jaxws 2.1 and the jaxws-api available at repo1.maven.org is
> not the same with the Sun's one (both pom and the jar )
> I am working jaxws-maven-plugin and the generate code crash due to missing
> interfaces
> We can either sync the sun version over, or remove it from repo1 to remove
> confusion
> Here is the link to java.net repo
> https://maven-repository.dev.java.net/nonav/repository/com.sun.xml.ws/
--
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
