Update documentation (#2451)
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>
This commit is contained in:
13
pom.xml
13
pom.xml
@@ -542,24 +542,15 @@
|
||||
|
||||
<profiles>
|
||||
<profile>
|
||||
<id>nexus_staging</id>
|
||||
<id>publish</id>
|
||||
<activation>
|
||||
<property>
|
||||
<name>!skipNexusStaging</name>
|
||||
<name>!skipPublish</name>
|
||||
</property>
|
||||
</activation>
|
||||
<build>
|
||||
<plugins>
|
||||
<plugin>
|
||||
<!-- Use the Nexus Staging plugin as a full replacement
|
||||
for the standard Maven Deploy plugin. See https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
|
||||
why this makes sense :-) We can control whether we want to deploy to the
|
||||
Eclipse repo or Maven Central by a combination of the version being a SNAPSHOT
|
||||
or RELEASE version and property skipNexusStaging=true/false. In any case
|
||||
we can take advantage of the plugin's "deferred deploy" feature which makes
|
||||
sure that all artifacts of a multi-module project are deployed as a whole
|
||||
at the end of the build process instead of deploying each module's artifacts
|
||||
individually as part of building the module. -->
|
||||
<groupId>org.sonatype.central</groupId>
|
||||
<artifactId>central-publishing-maven-plugin</artifactId>
|
||||
<version>${central.publishing.maven.plugin.version}</version>
|
||||
|
||||
Reference in New Issue
Block a user