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 #.

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.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to