After adding the scm tags to the subproject (identical to the ones in parent) I was able to run
mvn release:prepare mvn release:perform Mvn indicated success for both. During the prepare task I got the following warning twice: [WARNING] Ignoring unrecognized line: ?? provisioning/typehandlerspace/pom.xml.releaseBackup [WARNING] Ignoring unrecognized line: ?? provisioning/typehandlerspace/release.properties However the release (non-snapshot) version was not committed so that what go deployed was the SNAPSHOT version. Locally the pom has been changed to the next development version. We really should urgently release this module so that we can then release working launchers again. So help for the release process would be very much appreciated. Cheers, Reto On Sat, Aug 23, 2014 at 8:23 PM, Reto Gmür <[email protected]> wrote: > So I was trying to prepare a release for the typerendeing feature which is > brken in the last released version. > > Running mvn release:prepare in provisioning/typerendering fails with the > following: > > .... > [INFO] Working directory: > /home/reto/projects/apache/clerezza/provisioning/typehandlerspace > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 47.822 s > [INFO] Finished at: 2014-08-23T20:17:20+01:00 > [INFO] Final Memory: 15M/242M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on > project typehandlerspace: Unable to tag SCM > [ERROR] Provider message: > [ERROR] The git-push command failed. > [ERROR] Command output: > [ERROR] fatal: repository ' > https://git-wip-us.apache.org/repos/asf/clerezza.git/typehandlerspace/' > not found > [ERROR] -> [Help 1] > > > It would be handy if the parennt pom could be configured to set the scm > tag so that this isn't extended by the inheriting projects. > > Of course we wouldn't have this problem if we would always do full > releases or if (my preferred variant) we would have diifferent git repos > for each module. > > Cheers, > Reto >
