Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Migration to Jakarta installation of Nexus
Following up on Dmitry's offline note here so everyone is in the loop.

Terry,

Looks like we have something staged and ready to go:


Go ahead and turn the sync on to Maven Central.


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On Jan 10, 2020, at 6:45 AM, Terry Yanko <tyanko@xxxxxxxxxxxx> wrote:

Thanks for the update Bill!

On Thu, Jan 9, 2020 at 7:39 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
We're moving kind of slow with validating the new configuration.  I'm still waiting for a new version of the parent pom that contains the configuration information to be released, so I can update one of my projects to use the new parent pom with the new configuration and prove that releases still work as expected.  Hopefully this will all come together tomorrow.

Terry Yanko wrote on 1/9/20 12:10 PM:
Hi All, 

How goes the testing on the jakarta.oss.sonatype.org instance? Are we safe to disable access on oss.sonatype.org for the migrated user accounts? Anything we can do on our end to offer support?

Best, 

Terry 


On Tue, Dec 17, 2019 at 11:00 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
All,

We've struggled with the 30 day expiration of oss.sonatype.org.  Sonatype has very generously agreed to dedicate an instance of Nexus Pro specifically to us and our Jakarta efforts that will give us a 60 day retention policy.

Here's the information I have:

- Thursday, January 2nd new instance available for testing at jakarta.oss.sonatype.org

- Monday, January 6th cutover -- publishing to Central from oss.sonatype.org will cease to work

- Users in the "Migrate" tab will be migrated.  Users in the "Hold" tab are welcome to opt-in (there will be another batch)
  https://docs.google.com/spreadsheets/d/10eQJ46CyqcK8lco2z8dEN_9c29Wql_E_eSU8feYejcQ/edit?usp=sharing

I haven't confirmed, but I assume all users will still work as-is, same password, just with jakarta.oss.sonatype.org instead of oss.sonatype.org.

In that regard the migration should be fairly simple.  However we still need a volunteer to update the EE4J parent pom.  Any takers?

Terry, is there a sneaky way we could do that now if someone was motivated?  Maybe publish it and just not use it till January?


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

_______________________________________________
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


Back to the top