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
Hi David, 

On an unrelated note, are you by chance (or someone on this thread) responsible for maintaining the org.glassfish.jaxb project, particularly wrt to publishing to Central? A co-worker reached out this morning and mentioned that a version of this artifact that is apparently missing from Central. I thought that since we were already connected I would raise the issue here in case someone would like to publish the missing version.

Link to project: https://search.maven.org/artifact/org.glassfish.jaxb/txw2
missing version: 2.4.0-b180608.0325 

Best, 

Terry

On Thu, Jan 2, 2020 at 12:35 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
Thanks, Terry.  We're on the receiving side of this gift, so whatever you need we'll make it work.

Thank you so much for the update.  Hope you and the team had a great holiday!

On Jan 2, 2020, at 9:31 AM, Terry Yanko <tyanko@xxxxxxxxxxxx> wrote:

Hi David, 

I apologize, but with the holidays and a number of folks out on vacation it doesn't look like we'll have the testing instance up today. Likely a more realistic schedule would be Monday for having the test instance ready, and the cutover actually taking place later in the week on Thursday. Would that work for you? 

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

Back to the top