Re: [ee4j-build] [jakartaee-spec-project-leads] Can Maven Central artifa

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Hi Gunnar,
Jim created an
OSSRH issue related to this problem...  I updated it over the weekend
with this comment, which better describes the issue:
https://issues.sonatype.org/browse/OSSRH-51386?focusedCommentId=806172&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-806172

Basically, we
have some artifacts in Maven Central that can not reference its parent
pom.  We still don't understand the exact reasons why the parent poms
were not properly deployed.  This lack of the parent poms are affecting
access of the api artifacts for at least jaxr and management api.  And,
it's preventing these artifacts from getting mirrored to the other maven
repos.

We think a "simple"
workaround is to just modify the poms for these api artifacts to point
an existing parent pom and re-deploy.  But, we don't think this re-deploy
with the same version will work due to the reasons you cited below.  

We're just trying
to figure out how to clean this up...  Any suggestions would be appreciated.
 Thanks!

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Gunnar
Morling <gmorling@xxxxxxxxxx>
To:
       JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Cc:
       EE4J
build and releng discussions <ee4j-build@xxxxxxxxxxx>
Date:
       09/09/2019
11:01 AM
Subject:
       [EXTERNAL]
Re: [jakartaee-spec-project-leads] Can Maven Central artifacts    
   be        overwritten?
Sent
by:        jakartaee-spec-project-leads-bounces@xxxxxxxxxxx

---

Hi Jim, 

It's my understanding that once something has been released to Maven Central,
it cannot be modified or removed. I.e. if there's something wrong with
a released artifact, a new release (with a new version) must be done. 

That said, I'm not sure what "failed to be written to the mirror sites"
means; which sites are these, maybe the mirroring itself can be re-triggered,
if the actual artifacts themselves are good? 

--Gunnar 


----- Original Message ----- 

> From: "Jim Krueger" <jckofbyron@xxxxxxxxx>
> To: jakartaee-spec-project-leads@xxxxxxxxxxx, "EE4J build and
releng
> discussions" <ee4j-build@xxxxxxxxxxx>
> Sent: Friday, 6 September, 2019 8:45:11 PM
> Subject: [jakartaee-spec-project-leads] Can Maven Central artifacts
be
> overwritten?

> Hi,
> I'm currently working through a problem where the jakarta ee artifacts
for
> the management-api and jaxr projects were released to maven central,
but
> failed to be written to the mirror sites.

> Question: Is it allowable to run my release jenkins job again to overwrite
> the the artifacts in maven central or does Sonatype need to clean
these up
> before I can re-submit my job?

> Thanks

> _______________________________________________
> jakartaee-spec-project-leads mailing list
> jakartaee-spec-project-leads@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads