I adopted the action to publish the artifact release into two repositories by calling mvn deploy twice with different profiles. I believe this is the best approach available, since any other attempts to simulate the Maven run might fail... I also believe it is better than tinkering with .index file as it is currently done in the snapshot release.
Bernd,
I adopted the action to publish the artifact release into two repositories by calling
mvn deploytwice with different profiles. I believe this is the best approach available, since any other attempts to simulate the Maven run might fail... I also believe it is better than tinkering with.indexfile as it is currently done in the snapshot release.Changes
I added an additional variable
central-release-profilewith a default value pointing tooss-maven-centralwhich is the name of the profile fromcommunity-hub-release-parentafter applying changes of https://github.com/camunda-community-hub/community-hub-release-parent/pull/10The release task is calling Maven twice (with Central release profile and without) in order to deploy to Camunda repository and then to Maven Central.
Please merge and release 1.0.9
Cheers,
Simon