Merge branch 'jann0k/exists-maven-plugin' into 'master'

RM-3338: use exists-maven-plugin

See merge request cdoc2/cdoc2-java-ref-impl!35

Author: jann0k

README.md

@@ -187,7 +187,7 @@ Example `<profile>` section of `settings.xml` for using cdoc2 dependencies:
   </profile>
 ```
 
-Note: When pulling, the [package index is based on the organization level](https://stackoverflow.com/questions/63041402/github-packages-single-maven-repository-for-github-organization)
+Note: When pulling, the [GitHub package index is based on the organization level](https://stackoverflow.com/questions/63041402/github-packages-single-maven-repository-for-github-organization)
 , not the repository level.
 
 So defining any Maven package repo from `open-eid` is enough for pulling cdoc2-* dependencies.
@@ -253,3 +253,20 @@ See [cdoc2-cli/README.md](cdoc2-cli/README.md)
 
 See [VERSIONING.md](VERSIONING.md)
 
+## Publishing
+
+### GitHub
+
+Create release on tag done by VERSIONING.md process. It will trigger `maven-release.yml` workflow that
+will deploy Maven packages to GitHub Maven package repository.
+
+### Manual
+
+Since build uses `exists-maven-plugin` then `altDeploymentRepository` doesn't work as it only works 
+for `deploy` plugin. Set `project.distributionManagement` user properties instead:
+```
+mvn deploy -Dproject.distributionManagement.repository.id=github \
+-Dproject.distributionManagement.repository.url=https://maven.pkg.github.com/open-eid/cdoc2-java-ref-impl`
+```
+
+

cdoc2-cli/pom.xml

@@ -4,7 +4,7 @@
     <parent>
         <artifactId>cdoc2</artifactId>
         <groupId>ee.cyber.cdoc2</groupId>
-        <version>1.3.0</version>
+        <version>1.4.0-SNAPSHOT</version>
     </parent>
 
     <artifactId>cdoc2-cli</artifactId>

cdoc2-client/pom.xml

@@ -4,7 +4,7 @@
     <parent>
         <artifactId>cdoc2</artifactId>
         <groupId>ee.cyber.cdoc2</groupId>
-        <version>1.3.0</version>
+        <version>1.4.0-SNAPSHOT</version>
     </parent>
 
     <artifactId>cdoc2-client</artifactId>

cdoc2-lib/pom.xml

@@ -3,7 +3,7 @@
     <parent>
         <artifactId>cdoc2</artifactId>
         <groupId>ee.cyber.cdoc2</groupId>
-        <version>1.3.0</version>
+        <version>1.4.0-SNAPSHOT</version>
     </parent>
     <modelVersion>4.0.0</modelVersion>
 
@@ -20,7 +20,7 @@
         <dependency>
             <groupId>ee.cyber.cdoc2</groupId>
             <artifactId>cdoc2-schema</artifactId>
-            <version>1.2.0</version>
+            <version>1.3.0-SNAPSHOT</version>
         </dependency>
 
         <dependency>

cdoc2-schema/pom.xml

@@ -3,13 +3,13 @@
     <modelVersion>4.0.0</modelVersion>
 
     <parent>
-        <version>1.3.0</version>
+        <version>1.4.0-SNAPSHOT</version>
         <groupId>ee.cyber.cdoc2</groupId>
         <artifactId>cdoc2</artifactId>
     </parent>
 
     <artifactId>cdoc2-schema</artifactId>
-    <version>1.2.0</version>
+    <version>1.3.0-SNAPSHOT</version>
 
     <description>CDOC2 flatbuffer schemas and related functionality </description>
 
@@ -159,14 +159,6 @@
                     </execution>
                 </executions>
             </plugin>
-            <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-deploy-plugin</artifactId>
-                <version>3.1.1</version>
-                <configuration>
-                    <skip>false</skip>
-                </configuration>
-            </plugin>
         </plugins>
     </build>
 

pom.xml

@@ -3,7 +3,7 @@
 
     <modelVersion>4.0.0</modelVersion>
 
-    <version>1.3.0</version>
+    <version>1.4.0-SNAPSHOT</version>
     <groupId>ee.cyber.cdoc2</groupId>
     <artifactId>cdoc2</artifactId>
     <description>CDOC2 reference implementation </description>
@@ -291,13 +291,36 @@
                 </executions>
             </plugin>
 
+            <!-- if exact RELEASE version of module already exists, -->
+            <!-- then skip deployment by setting maven.deploy.skip=true property for that module -->
+            <!-- GitHub doesn't allow overwriting existing RELEASE modules and deploy will fail with HTTP 409 -->
+            <plugin>
+                <groupId>org.honton.chas</groupId>
+                <artifactId>exists-maven-plugin</artifactId>
+                <version>0.13.0</version>
+                <executions>
+                    <execution>
+                        <phase>install</phase>
+                        <goals>
+                            <goal>remote</goal>
+                        </goals>
+                        <configuration>
+                            <!-- run only if deploy goal is specified in maven command line -->
+                            <requireGoal>deploy</requireGoal>
+                        </configuration>
+                    </execution>
+                </executions>
+                <configuration>
+                    <failIfNotMatch>false</failIfNotMatch>
+                    <userProperty>true</userProperty>
+                    <!--skip>true</skip-->
+                </configuration>
+            </plugin>
+
             <plugin>
                 <groupId>org.apache.maven.plugins</groupId>
                 <artifactId>maven-deploy-plugin</artifactId>
                 <version>3.1.1</version>
-                <configuration>
-                    <skip>false</skip>
-                </configuration>
             </plugin>
 
         </plugins>