Details
-
Type:
Bug
-
Status: New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: staging-maven-plugin
-
Labels:
Description
When resetting maven deploy configuration (https://github.com/sonatype/nexus-maven-plugins/blob/f1be87efb0d476a4305b77d405bd3ddfb30ba5bf/staging/maven-plugin/src/main/java/org/sonatype/nexus/maven/staging/deploy/DeployLifecycleParticipant.java#L132) the configuration is not handled which means it is lost and part of it has no equivalent in the plugin so it is impossible to use nexus staging plugin properly in some cases in big automated suites.
One typical case is when release profiles are plural (because triggered manually outside of a release plus in a release).
Being able to at least specify a list of active profile in the plugin - or not loose them reusing maven deploy plugin lifecycle and just replace the actual deployment if preferred - would be neat.
In any case, the lost features should at least be logged with a warning and not silently swallowed which lead to broken (valid for nexus) releases (missing artifacts typically).