User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
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; 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.
Scott Stark wrote on 1/14/20 6:58 PM:
I'm not able to release to the oss.sonatype.org
repo using the cdi-bot@xxxxxxxxxxx login, and I'm
not able to access the org.eclipse.ee4j:project:1.0.6 parent pom
either. Are we in some transitional state right now?
Sounds great. Before we turn on the sync to Maven
Central I just wanted to confirm that we are OK to disable
access to oss.sonatype.org
for the following users:
The reason we prefer to approach the migration this way
is so that we can mitigate any possibility of duplicate
writes to Central which can be a headache to clean up. If
we are clear to revoke access, let me know and we will
turn on sync ASAP.
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?
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.