I don't think this will fix the issue.
SCM 1.8.1[1] is not related to GIT 1.8.x
It's a coincidence that the most recent version of SVN, GIT and SCM are
all 1.8.x
Robert
[1]
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18930
Op Thu, 26 Dec 2013 10:59:42 +0100 schreef Mark Derricutt
<m...@talios.com>:
My guess is you've got a new/recent git?
If so, you'll need to add:
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.8.1</version>
</dependency>
</dependencies>
so that you get the new version that actually picks up modified files (
git 1.8.x finally drops the leading # from its output and broke the old
scm provider.
On 26 Dec 2013, at 1:28, Martijn Dashorst wrote:
I have tried to revert to maven-release-plugin:2.3.2 (the 6.12.0
release was baked with this one), I have tried to apply apache-parent
pom v13, and both failed with the same result.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
