maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <>
Subject Re: maven-release-plugin oddity - no git commit under mvn 3.1.1
Date Mon, 09 Dec 2013 21:33:54 GMT

Here's a list of the maven-release-plugin and the matching SCM versions.

m-release-plugin:2.3.2 depends on scm:1.7
m-release-plugin:2.4 depends on scm:1.8 (standard upgrade, incl. SCM-686)
m-release-plugin:2.4.1 depends on scm:1.7 (back due to MRELEASE-830,  
SCM-709 )
m-release-plugin:2.4.2 depends on scm:1.7

SCM-686 introduced the porcelain option. However, suddenly all releases  
where evaluated/tagged from the root of the repository instead of the root  
of the project. This broke a lot of projects, more compared to the  
addition of porcelain, so I decided to fall back to 1.7.
SCM-709 is probably fixed by now, but I'm still missing the feedback. I've  
closed it as part of SCM 1.9, so I'll include it with the next m-release-p.


Op Mon, 09 Dec 2013 11:56:21 +0100 schreef Olivier Lamy <>:

> On 9 December 2013 20:48, Mark Derricutt <> 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.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message