Hi
Good catch regarding the documentation, which needs some updating.
If I remember correctly, we decided not to use this staging process long 
ago.
I cannot find any discussion, though.
But I can remember cutting release without this for a long time now.


On Tuesday, 29 July 2025 at 1:46:39 am UTC+10 [email protected] wrote:

> Just for the record, as I have done this on another project. When you 
> login to the Maven Central portal, you have to use username and password 
> from the OSS Nexus, which was migrated. If you want to start using your 
> GtiHub for login, just write an email to Maven Central support, they answer 
> quite well. I wrote a blog about the experience, it might help someone, 
> despite I did not use Njord but the official plugin.
> https://omnifish.ee/big-changes-in-maven-central/#local-deployment
>
> I guess the deployment to staging already stopped working, am I right? The 
> page should be updated ... 
> https://www.mojohaus.org/development/performing-a-release.html#Staging_the_Release
> However I think we can see all deployments of each other, so "the last 
> review" still can be done somehow.
>
> David Matějček
>
> On Monday, 2 June 2025 at 22:57:29 UTC+2 [email protected] wrote:
>
>> Hi, 
>>
>> org.codehaus.plexus and org.codehaus.modello have been migrated to 
>> the Central Portal. 
>> https://central.sonatype.com/publishing/ 
>>
>> Some current release managers can lose access - please, check and 
>> contact on ASF slack #mojohaus channel or directly with Sonatype 
>> support. 
>>
>> New parent pom 22 - was release: 
>> https://github.com/codehaus-plexus/plexus-pom/releases/tag/plexus-22 
>> https://codehaus-plexus.github.io/plexus-pom/ 
>>
>> -- 
>> Sławomir Jaranowski 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/mojohaus-dev/b0cf0eda-1560-4beb-b582-ef88e126e64an%40googlegroups.com.

Reply via email to