Merge pull request #261 from focus-shift/260-upload-artefacts

Do not add test module on -Drelease

.github/workflows/release.yml

@@ -26,7 +26,7 @@ jobs:
       - name: Build with Maven
         run: >
           ./mvnw $MAVEN_CLI_OPTS
-          -Prelease
+          -Prelease -Drelease
           clean deploy
         env:
           OSSRH_USERNAME: ${{ secrets.OSSRH_USERNAME }}

jollyday-tests/pom.xml

@@ -77,23 +77,4 @@
       </plugin>
     </plugins>
   </build>
-
-  <profiles>
-    <profile>
-      <id>release</id>
-      <build>
-        <plugins>
-          <plugin>
-            <groupId>org.sonatype.plugins</groupId>
-            <artifactId>nexus-staging-maven-plugin</artifactId>
-            <version>1.6.13</version>
-            <configuration>
-              <skipNexusStagingDeployMojo>true</skipNexusStagingDeployMojo>
-            </configuration>
-          </plugin>
-        </plugins>
-      </build>
-    </profile>
-  </profiles>
-
 </project>

pom.xml

@@ -44,7 +44,6 @@
   <modules>
     <module>jollyday-core</module>
     <module>jollyday-jaxb</module>
-    <module>jollyday-tests</module>
   </modules>
 
   <developers>
@@ -338,5 +337,24 @@
         </plugins>
       </build>
     </profile>
+
+    <profile>
+      <id>no-release</id>
+      <!--
+      According to https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
+      skipNexusStagingDeployMojo may not be set to true in the last reactor module. Because we don't
+      want to deploy our last module, nor a dummy module, we simply omit the relevant modules when
+      a deployment is in progress.
+      -->
+      <activation>
+        <property>
+          <name>!release</name>
+        </property>
+      </activation>
+      <modules>
+        <module>jollyday-tests</module>
+      </modules>
+    </profile>
+
   </profiles>
 </project>