On 9 December 2013 20:48, Mark Derricutt <[email protected]> wrote: > I was speaking with Olivier on IRC earlier, so far I've managed to work > around the issue by adding a <dependency/> on the latest > maven-scm-providers-gitexe inside my maven-release-plugin <plugin/> block and > that seems to have resolved the issue. > > Simply dropping back to 2.3.2 of the release plugin didn't help as that still > picked up the older maven-scm version which was looking for a git status > output starting with #. >
Yup correct. I hope we avoid such issue when using jgit provider (if it's released one day) > Mark > > On 9 Dec 2013, at 22:00, Stephen Connolly wrote: > >> There is a know issue with Git and release plugin 2.4.2 and something to do >> with SCM version bundled in Maven 3.1.1? (or maybe 3.1.x) Olivier may know >> more. AFAIK scm is not bundled with core. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
