maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Sandoz (JIRA)" <>
Subject [jira] Commented: (MAVENUPLOAD-2651) Please re-upload*:1.1 on from
Date Wed, 04 Nov 2009 08:59:55 GMT


Paul Sandoz commented on MAVENUPLOAD-2651:

Carlos, do you know who was responsible for requesting that the 311 artifact be deployed to
the central repository? We never made such a request.

I think this is going to cause serious developer confusion utilizing a different version (as
it will be different from the primary location of the maven repo). The artifact on
the central repo also contains a serious backwards compatibility bug, so compilation against
this artifact will result in runtime errors when deploying an application to a Java EE 6 compatible

Is there no procedure at all for updating an existing artfact, especially since the developers
responsible for that artfact were not responsible for the deployment request to the central

> Please re-upload*:1.1 on from
> ----------------------------------------------------------------------------------------------------------------------
>                 Key: MAVENUPLOAD-2651
>                 URL:
>             Project: Maven Upload Requests
>          Issue Type: Wish
>            Reporter: Jakub Podlesak
> Due to reasons described by Paul Sandoz (JSR-311 co-spec lead) in [1], we had to update
the above mentioned artifacts.
> Could you please update them on the central maven repository?
> ----- Quote from [1]: -----
> Previously when we distributed jsr311-api version 1.1 to the maven repo we naively
thought that the spec was done and dusted. However, we had to make some changes to accommodate
integration with Servlet 3.0.
> We do not anticipate any more changes. The maintenance review for 1.1 closes on the 1st
of Nov. But i need to make switch in the Jersey source now to prepare for the release (i will
send another email on that). 
> ----- End Quote -----
> Thanks,
> ~Jakub
> [1]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message