Mukul, if Xerces team were responsible to publish to maven central, all
these problems would disappear.
And, even if Adam and exist-db team are very kind and publish xerces
under their groupId, we - end users - have no guarantee that artifacts
published by others are the same that are published on xerces web page.
Would you rely on an MS Office update published by another organization
than Microsoft ?
Christophe
Le 24/01/2020 à 02:46, Mukul Gandhi gandhi(_dot_)mukul(_at_)gmail(_dot_)com a
écrit :
Hi Adam,
On Thu, Jan 23, 2020 at 8:13 PM Adam Retter adam(_dot_)retter(_at_)googlemail(_dot_)com
<mailto:adam(_dot_)retter(_at_)googlemail(_dot_)com>
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com
<mailto:xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>> wrote:
Sorry about that. Unfortunately I cannot update artifacts on Maven
Central, releases there are considered immutable.
It seems that, the only way to get errors fixed for a release on Maven
Central is to, request Sonatype via a jira issue and request them to
remove the offending artifacts (after which the corrected artifacts
can be republished). Following is an example of how such a request to
Sonatype should look like,
https://issues.sonatype.org/plugins/servlet/mobile#issue/MVNCENTRAL-218 ;(you
may need to determine the right URL for the Xerces 2.12.1 artifact on
the Maven Central server to tell to Sonatype, than what is suggested
on the preceding example URL I've cited).
It'd be great if you could get this done. Otherwise, we shall live
with this issue :)
--
Regards,
Mukul Gandhi
http://member.acm.org/~mukulgandhi
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/2837134>
(by email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--