To fix this I had to add
org.apache.maven.scm
maven-scm-provider-gitexe
1.9
to the plugin definition of the m-r-p (version 2.4.1).
Martijn
On Wed, Feb 5, 2014 at 5:44 PM, Martijn Dashorst wrote:
> This is still an issue. Can someone please fix the maven-release-plugin to
> w
This is still an issue. Can someone please fix the maven-release-plugin to
work with a decent version of git?
Martijn
On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte wrote:
> Hi,
>
> it depends on the type of problem you're facing.
>
> as said before, these are probably the best options:
>
> -
Hi,
it depends on the type of problem you're facing.
as said before, these are probably the best options:
- try maven-release-plugin 2.4
- use an older version of GIT with English locale.
For details see https://jira.codehaus.org/browse/MRELEASE-812
Robert
Op Sat, 28 Dec 2013 15:34:26 +0100 s
Hi,
I tried the workaround (release plugin 2.4.2 + maven-scm-provider-gitexe
1.8.1) without success, still messing up releases with snapshot versions.
I'm on git 1.8.5.2.
Am I missing something else ?
Here is my parent pom with the release profile I use if this can help:
https://gitorious.org/net
You're correct - 1.8.1 is not related to Git 1.8, however it is the latest
release - and a fix that SUPPORTS Git 1.8 was actually released back in
something like scm-provider 1.5 earlier in the year - only the Maven Release
Plugin DOES NOT USE IT.
We should really have a new release of m-r-p th
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
My guess is you've got a new/recent git?
If so, you'll need to add:
org.apache.maven.scm
maven-scm-provider-gitexe
1.8.1
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
provi
> To: users@maven.apache.org
> Subject: Re: Unable to use the maven-release-plugin to release
> Date: Wed, 25 Dec 2013 13:46:43 +0100
> From: rfscho...@apache.org
>
> Hi,
MG>Guten Tag
>
> the problem you're facing has to do with the version of the git-clie
Hi,
the problem you're facing has to do with the version of the git-client.
They've changed the output, which is parsed to detect commit differences.
We've tried to switch to the '--porcelain' option in m-release-p 2.4, but
that caused more problems. So that has been reverted in 2.4.1.
You ha
I'm currently in week 4 of trying to release Apache Wicket and I am giving up.
The release plugin fails to tag the updated release poms but instead
tags the SNAPSHOT version. Then the release plugin starts to release
the tag which unfortunately points to the SNAPSHOT version.
My best guess is tha
10 matches
Mail list logo
