maven-release-plugin works only perfectly for nested multi-module project. In case the modules projects are located inside the folder containing the pom.xml with the "pom" packaging.
In case the modules are located on the same level as the pom-project and need to be referenced like:
…you will get a misleading error message:
<modules> <module>../moduleA</module> <module>../moduleB</module> <module>../moduleC</module> </modules>
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM Provider message: The git-push command failed. Command output: ERROR: Repository not found. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
Moving the submodules to the folder containing the multi-module pom.xml solves the problem. The issue was extensively tested with releasing http://lightfish.adam-bien.com :-)
See you at Java EE Workshops at MUC Airport, and particularly at the http://workshops.adam-bien.com/javaee-architectures.htm!
Web Apps, SPA, PWA with vanilla Java Script (ES 6+), CSS 3 and WebStandards only. As simple as possible, but not simpler. See you at: (Progressive) Web apps, Single Page Apps and WebStandards airhacks workshops at MUC airport, Winter Edition
airhacks.fm the podcast:
Stay in touch: airhacks.news.