Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Incomplete
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Build Tooling
-
Labels:None
Description
In the past I've used the deploy plugin's skip functionality to exclude .war files in my project from being released (this is partly because they're not needed and partly because maven 3 produces invalid signatures for them - I suspect as a result of parallel builds).
Is there a way to configure the nexus-staging-maven-plugin in a similar way? This is what I used in the pom.xml of a module I didn't want to deploy:
<!-- No need to deploy this to Nexus --> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <configuration> <skip>true</skip> </configuration> </plugin> </plugins> </build>
I don't see anything in the docs about this, if it isn't available then I'd like to request that feature
Note: another used tested with various skip parameters, and conclusion is "If you use the staging system during build and the module you skip like that happens to be the last in the reactor, ALL deploys will be skipped."
Migrated from
https://github.com/sonatype/nexus-maven-plugins/issues/65