dev@jax-ws.java.net

Who releases the jaxws-api artifact? (to http://repo1.maven.org/maven2/)

From: Paulo Gaspar <paulo.gaspar_at_gmail.com>
Date: Wed, 18 Nov 2009 15:49:23 +0000

Hi again,


The bottom of the problem is that two different versions of the "jaxws-api-2.1" artifact were released:

- The one at "maven.org" only works with Java6, missing dependencies (POM) and classes (jar) to work on Java 5;
    http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1/

- The other at "java.net" works for Java 5 fine.
    http://download.java.net/maven/1/javax.xml.ws/


I am still interested in knowing who can fix this or how.

In case it is out of your hands, I volunteer to prepare a note to add to your Maven build documentation.


Best regards,
Paulo Gaspar

On 2009-11-18, at 14:19, Paulo Gaspar wrote:

> Hi again,
>
>
> It seems that only "jaxws-api-2.1.pom" was changed together with the "jaxws-api-2.1.jar".
>
> I would still like to know:
>
> 1) If the above mentioned archives are released by this project;
>
> 2-Yes) If Yes, if you intend to repeat the stunt of silently changing released archives;
>
> 2-No) If no, I would like to know who did this, so that I can try knock at their door.
>
>
> Thanks,
> Paulo Gaspar
>
>
> On 2009-11-18, at 13:49, Paulo Gaspar wrote:
>
>> Hi,
>>
>>
>> Some of my project's Java 5 Maven builds recently broke due to changes on RELEASED archives.
>>
>> At the moment I already detected that the "jaxws-api-2.1.jar" archive had a class removed:
>> javax.xml.ws.spi.WebServiceFeatureAnnotation
>>
>> ...but there are other differences (jsr181-api and jsr250-api) related, since dependency on these modules must now be explicitly declared on my POMs.
>>
>>
>> I understand that the new "version" might work (maybe even better) with Java 6, but the archives I am using have RELEASE names, which means they were RELEASED (are not snapshots) and, therefore, should NOT be changed.
>>
>> Good and expected practice is that you do NOT change a released archive. You may cut a new version with fixes and even remove de old version, but you do not silently change a released archive.
>>
>>
>> I am assuming that (at least) the above mentioned problem has the end of this project, since this is the reference implementation. If it is not so, please and you have nothing to do with this mess, I am sorry for knocking at the wrong door but please point me to the right one.
>>
>> Besides this issue, if you are aware of these changes, please tell me (or point me to) what else changed.
>>
>>
>> Thank you and my best regards,
>> Paulo Gaspar
>