Cannot perform release and process under documented

[line-o]

While releasing 4.2.3 several issues in its process became apparent

• missing ARM docker images mean that one needs to add -Darguments="-Dexist.processor.version=6.4.0" in order to be able to advance when releasing on an ARM machine (like current MacBooks)
• under documented release requirements
  • no mention of necessary GPG key for signing jars
  • no mention of maven central credentials being required
• even if all of the above is in place the deployment will fail due to missing sources and javadocs in the bundle that is uploaded to maven central
• package.json and package-lock.json still have version property set and this is also bumped as part of the release process

[line-o]

Do we even need to deploy JARs to maven central?
Do we know of anyone depending on the jars of this project?

[line-o]

If yes, we need to add the following to the pom:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-javadoc-plugin</artifactId>
        <version>3.10.1</version> <!-- Check for latest version at Maven Central -->
        <executions>
          <execution>
            <id>attach-javadocs</id>
            <goals>
              <goal>jar</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-source-plugin</artifactId>
        <version>3.3.1</version>  <!-- Check for latest version at Maven Central -->
        <executions>
          <execution>
            <id>attach-sources</id>
            <goals>
              <goal>jar-no-fork</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

[duncdrum]

@line-o switching the container image to duncdrum/existdb would reenable releasing on ARM, until we can populate all tags with multi-arch images.

[adamretter]

under documented release requirements

• no mention of necessary GPG key for signing jars
• no mention of maven central credentials being required

That is the same for all eXist-db projects that build using Maven - documentation is here: https://github.com/eXist-db/exist/blob/develop/exist-versioning-release.md

even if all of the above is in place the deployment will fail due to missing sources and javadocs in the bundle that is uploaded to maven central

That is a regression caused by this recent change to Monex not being done correctly - #324

missing ARM docker images

Someone would need to add an ARM Docker Image for eXist-db here: https://github.com/eXist-db/exist/tree/develop/exist-docker

[line-o]

Also, using -Darguments="-Dexist.processor.version=6.4.0" does effectively also set the minimum processor version in the released XAR package!