No one ever did answer this question so here's my guess...
The "snapshots" profile should be used only what pushing out SNAPSHOT artifacts.
The "staging" profile should be used when staging a final release for
review, before finally releasing it.
The "oss-release" profile should be used only when doing a final release
of a reviewed and approved artifact.
The "oss-release" profile is the only one that signs the artifacts.
This is used for any "Maven release" that goes to Maven Central, final or not final.
If I'm using the nexus-staging-maven-plugin to stage my release so that
it can be verified, and then to later close the staging repository and
finally release it, do I need to use the "oss-release" profile to do that?
The "oss-release" profile adds a lifecycle (i.e plugin executions) that is not desirable for this use-case.
The base configuration of the plugin can be done in the default profile (i.e no profile).
If so, I'm not sure when the "staging" profile would be used.
IIUC the current direction seems to decouple the nexus workflow in 2 steps:
- deploy to a staging repository and close the staging repository
- release the staging repository once reviewed/approved
I.e If activated, one can consume artifacts from any closed staging repository.
If the review/approval depends on automated test suites, they will likely need to consume the artifacts from the staging repository.
My understanding is that you can select multiple profiles with Maven,
so there's no *need* to rename existing profiles to match the names above.
For example, I should be able to do
$ mvn -Psnapshots -Pdeploy-snapshot clean install deploy
Is that correct?
Yes.
You can also do -Psnapshots,deploy-snapshots
Bill Shannon wrote on 10/12/18 12:39 PM:
> The EE4J parent pom defines three profiles:
>
> - oss-release
> - snapshots
> - staging
>
> When should each of these be used?
>
> Many of our existing projects define profiles that were used to release
> artifacts at maven.java.net. Should these profiles all be renamed to
> extend one of the profiles above to benefit from the shared configuration
> in the parent pom?
> _______________________________________________
> ee4j-build mailing list
> ee4j-build@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-build
>
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build
