[
https://issues.apache.org/jira/browse/HIVE-21512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804640#comment-16804640
]
Zoltan Haindrich commented on HIVE-21512:
-----------------------------------------
sonatype have resolved my ticket with the following explanation...
```
Sonatype policy prohibits the removal or other modification of artifacts once
they've been published to Central. The reasoning behind this is that if the
artifact changes after publication, any builds that already depend on it will
break. Our recommendation in situations like this is for you to deploy a
corrected version and inform your user base to avoid the incorrect version.
```
it seems like they don't care that at some point that artifact must have been
there...
> Upgrade jms-api to 2.0.2
> ------------------------
>
> Key: HIVE-21512
> URL: https://issues.apache.org/jira/browse/HIVE-21512
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Attachments: HIVE-21512.01.patch, HIVE-21512.01.patch,
> HIVE-21512.01.patch
>
>
> I've noticed that for some time that sometimes there are issues with
> javax.jms:jms:1.1 artifact - because it doesn't seem to be available from
> maven central for some reason;
> https://issues.sonatype.org/browse/MVNCENTRAL-4708
> Alternatively; I think we might try to just upgrade to 2.0.2 version of the
> jms-api.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
