Maven Evangelism

They messed up, you can see how they kept changing the jar
https://maven-repository.dev.java.net/source/browse/maven-repository/www/repository/javax.xml.ws/jars/jaxws-api-2.1.jar

So what should we do? having the old jaxws-api-2.1 is also bad. Perhaps repo1 should leave the bussiness of maintinaing that jar to java.net

that's what i did, but they changed it after sync, what can I do ?
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

Can you remove it from repo1?

no, it's policy not to remove anything unless it's clearly unusable.

I beleive it is unuable since the the jaxws-api at java.net has the correct dependencies and the jar at jaxws-api at java.net has more interfaces. The user of jaxws-maven-plugin is blocked from using this plugin since jaxws-api at repo1 is picked up first.

The fact that it's incorrect doesn't make it unusable. Unusable means jar corrupt or empty.
wdym about jaxws-maven-plugin problem? the central repo has to be self contained, the plugin can't be releasing depending on stuff in other repos

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?

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

Seems that this issue should be WONTFIX -> request 2.1-1 release. Sound right?

right

This isn't good. My pom refers to both repo1 and java.net. I don't have any means to specify where jaxws-2.1 should be taken from (and of course it's taken from wrong repository).

Marat, that's not our responsibility, by definition releases shouldn' t be changed on the repository, and they were changed at java.net repo

Marat, here is the work around

• install a good copy of javax-api at your internal repo.

• Use maven-proxy and configure it to pickup artifact at your internal repo first then repo1

On the second thought, It is a real pain for this setup. Can we make it as an exception??

the solution was already proposed, we can host a 2.1-1 with the right pom and jar, but somebody has to prepare and request it

Created upload request for a 2.1-1 version.

http://jira.codehaus.org/browse/MAVENUPLOAD-1786