Prepare for publishing vie the Central Portal

[slawekjaranowski]

fix: #350

[cstamas]

LGTM, one remark:
I'd name the server.id with longer (and more descriptive) name: sonatype-central-portal.

[slawekjaranowski]

LGTM, one remark: I'd name the server.id with longer (and more descriptive) name: sonatype-central-portal.

hehe - I have one, for mojohaus ... we can change also in mojohaus to have one configuration 😄

[cstamas]

Yes, instead as before, when every project "invented" their own server.id (and I manage many), hence my settings.xml was full of copy pasta of different server.id with same auth 😄

So I started doing this: name the thing we use as it is (and as benefit, have one entry in settings for all, instead many copies of same)

[cstamas]

Also @slawekjaranowski see this:
maveniverse/njord#24 (comment)

By using these 3 properties:

• no need to press Publish button
• build will fail if validation fails
• wait is few sec, as validation is quick

[kwin]

@cstamas What does that do? I thought that njord would only ever kick in if the distribution URI has scheme njord...

[cstamas]

This completely disables Njord (by not creating njord session), and hence no njord component will ever "kick in", as all of them start by checking the session existence.

Release profile enables it:
https://github.com/codehaus-plexus/plexus-pom/blob/master/pom.xml#L821-L822

This just makes sure that in "normal" operations Njord is not meddling for sure, and even in case of release, it as you say, only does "local staging" and later publishing.

[cstamas]

Unsure why was it done like it, as this really prevents Njord to stage snapshots for example, but that operation currently supports m-deploy-p as well, so no real need for Njord...