From fcb563dee0a426645cc9c1935869ac8e79f2426c Mon Sep 17 00:00:00 2001
From: Alexander Kriegisch <Alexander@Kriegisch.name>
Date: Sat, 15 May 2021 17:34:15 +0700
Subject: Fix selective Nexus deployment to Sonatype OSSRH

Other than Maven Deploy, Nexus Staging plugin cannot just be added to
the 'build/plugins' section of the parent POM once and (de-)activated
with a simple property like 'maven.deploy.skip' on a per-module basis.
See also https://issues.sonatype.org/browse/OSSRH-68966. Consequently,
we do not add it to the parent but separately to each module meant to be
published.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
---
 aspectjmatcher/pom.xml | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'aspectjmatcher')

diff --git a/aspectjmatcher/pom.xml b/aspectjmatcher/pom.xml
index ff456caa1..6dd942809 100644
--- a/aspectjmatcher/pom.xml
+++ b/aspectjmatcher/pom.xml
@@ -235,6 +235,12 @@
 				</executions>
 			</plugin>
 
+			<!-- Deploy this module to Nexus (Sonatype OSSRH, releases promotable to Maven Central) -->
+			<plugin>
+				<groupId>org.sonatype.plugins</groupId>
+				<artifactId>nexus-staging-maven-plugin</artifactId>
+			</plugin>
+
 		</plugins>
 	</build>
 
-- 
cgit v1.2.3