[ 
http://jira.codehaus.org/browse/MEV-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87378
 ] 

Carlos Sanchez commented on MEV-498:
------------------------------------

> jaxws-maven-plugin is in an odd situation where most of its dependencies are 
> in java.net maven1 repo.

everything in the central repo needs all dependencies in the central repo, so 
you have to ask for a push of what you need from the java.net repo before 
releasing the plugin.

> One of the dependency (jaxws-api) happen to be at repo1 as well.

see previous comment, all of them need to be in repo1

> Since repo1 is primary repo, its jaxws-api is picked up first and therefore 
> jaxws-maven-plugin is unusable.

same thing, released versions have to build against repo1 and only repo1

> 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.

as I said before: "the only thing that can be done right now is upload the good 
jar as version 2.1-1, state in the pom description that it's a fix of 2.1"

> Question, why does repo1 have a deployment of jaxws-2.1 way before it is 
> official released? 

there was an attempt to get java.net repo synced automatically and everything 
was pushed to repo1. For other problems like this now is no longer automatic, 
but the previous stuff is already there. It's not my fault if they change 
released versions in their repo which is a VERY BAD thing.




> 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

        

Reply via email to