Re: [ee4j-pmc] Migration to Jakarta installation of Nexus

["Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>]

Not an expert on maven etc. so what I say may be nonsense.  However my understanding is you have to push it yourself. We have a nexus job we used in the original Jakarta EE 8 release that "releases" from staging to central.

Steve

-----Original Message-----
From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx> On Behalf Of Mark Thomas
Sent: 31 January 2020 11:48
To: ee4j-pmc@xxxxxxxxxxx
Subject: Re: [ee4j-pmc] Migration to Jakarta installation of Nexus

On 15/01/2020 19:01, Terry Yanko wrote:
> Hi all,
> 
>  Ingestion services are back online and sync from Jakarta.oss to 
> Central is enabled. I see the release of the new parent pom
> here: https://repo1.maven.org/maven2/org/eclipse/ee4j/project/1.0.6/
> 
> You should be all set to release any additional content from the new 
> endpoint. Don't hesitate to reach out if any of you run problems with 
> the service. Once you're settled into your new publishing process I'd 
> recommend using https://issues.sonatype.org/projects/MVNCENTRAL/ to 
> raise any future questions or concerns related to the service as it 
> will be easier to rope in some of our other team members.

Quick question here before I raise an issue with sonatype.

How long are we expecting things to take to sync from this Nexus instance to Central? I released EL 4.0.0-RC1 ~18 hours ago and it hasn't sync'd yet. I don't want to raise an issue if this is normal / expected.

Mark


> 
> Thanks everyone for your patience, I hope jakarta.oss.sonatype.org 
> <http://jakarta.oss.sonatype.org> serves you well!
> 
> Best,
> 
> Terry
> 
> On Wed, Jan 15, 2020 at 12:44 PM Terry Yanko <tyanko@xxxxxxxxxxxx 
> <mailto:tyanko@xxxxxxxxxxxx>> wrote:
> 
>     Thanks for clearing that up, David! Sorry again for the confusion.
> 
>     The sync process setup is largely complete for jakarta.oss, however,
>     Central ingest is currently under maintenance due to a global HTTPS
>     cutover that took place this morning for Maven Central. Publishing
>     services are temporarily offline but we are working to remediate the
>     issue. I'll keep this group informed as I have more information.
> 
>     Best,
> 
>     Terry
> 
> 
>     On Wed, Jan 15, 2020 at 11:37 AM David Blevins
>     <dblevins@xxxxxxxxxxxxx <mailto:dblevins@xxxxxxxxxxxxx>> wrote:
> 
>         All,
> 
>         Here is our exact status.
> 
>          - At 7:50am Pacific yesterday Terry was given the go-ahead by
>         me here on this list on this thread
>          - At 9:55am Pacific there was a HEADS UP email by Dmitry
>         indicating there would not be a go-head till the 15.
> 
>         Unfortunately yesterday there were several private threads
>         started that confused the situation.
> 
>         We are in mid transition.
> 
>         At this point we need to let Terry work and not bombard him with
>         "why doesn't it work" questions.  We need to get him a day of
>         quiet so he can finish the process that was started at 7:50 am
>         yesterday.
> 
> 
>         DO NOT respond on any private threads or start new public
>         threads.  Terry, if you get any offline communication, ignore it.
> 
> 
>         -- 
>         David Blevins
>         http://twitter.com/dblevins
>         http://www.tomitribe.com
> 
> 
>>         On Jan 15, 2020, at 8:14 AM, Scott Stark <starksm64@xxxxxxxxx
>>         <mailto:starksm64@xxxxxxxxx>> wrote:
>>
>>         Shouldn't existing builds be able to see the 1.0.6 parent pom
>>         when building in the CI environment? The dependency-injection
>>         poms only reference the org.eclipse.ee4j:project parent pom
>>         for the release and staging repository information. As far as
>>         I know there is not anything in the CDI CI environment
>>         settings.xml that overrides this, but when I'm trying a
>>         testbuild of the api project with the following parent:
>>
>>         <parent>
>>           <groupId>org.eclipse.ee4j</groupId>
>>           <artifactId>project</artifactId>
>>           <version>1.0.6</version>
>>           <relativePath />
>>         </parent>
>>         the build is not able to resolve that parent.
>>
>>         On Wed, Jan 15, 2020 at 1:22 AM Bill Shannon
>>         <bill.shannon@xxxxxxxxxx <mailto:bill.shannon@xxxxxxxxxx>> wrote:
>>
>>             Yes, we're in a transitional state.
>>
>>             The new parent pom hasn't been published yet.
>>
>>             You should still be able to deploy to oss.sonatype.org
>>             <http://oss.sonatype.org/>; that access isn't supposed to
>>             be removed until tomorrow (Jan 15).
>>
>>             But, rather than moving backwards and trying to fix that,
>>             I think we should keep moving forwards and fix it as
>>             necessary with the new Nexus at jakarta.oss.sonatype.org
>>             <http://jakarta.oss.sonatype.org/>.
>>
>>         _______________________________________________
>>         ee4j-pmc mailing list
>>         ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
>>         To change your delivery options, retrieve your password, or
>>         unsubscribe from this list, visit
>>         https://www.eclipse.org/mailman/listinfo/ee4j-pmc
> 
> 
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc
> 

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