[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-pmc] Migration to Jakarta installation of Nexus
|
If "cease to work" includes *all* projects, we should actively inform all
projects. Not everybody uses the parent pom.
-Markus
-----Ursprüngliche Nachricht-----
Von: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] Im
Auftrag von David Blevins
Gesendet: Mittwoch, 18. Dezember 2019 05:00
An: EE4J PMC Discussions; Terry Yanko; Mikael Barbero
Betreff: [ee4j-pmc] Migration to Jakarta installation of Nexus
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_eSU8
feYejcQ/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
