You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Martijn Dashorst <ma...@gmail.com> on 2013/12/25 13:28:26 UTC
Unable to use the maven-release-plugin to release
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 that Maven fails to commit the updated release poms
and continues to tag and release the 6.13.0-SNAPSHOT versions.
I have upgraded to maven 3.1.1, the release plugin runs at 2.4.2 and
our specified configuration is:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.2</version>
<inherited>true</inherited>
<configuration>
<pushChanges>false</pushChanges>
<tagNameFormat>wicket-@{project.version}</tagNameFormat>
<updateWorkingCopyVersions>false</updateWorkingCopyVersions>
</configuration>
</plugin>
When merged with the Apache parent pom (v10), this results in:
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.4.2</version>
<inherited>true</inherited>
<configuration>
<pushChanges>false</pushChanges>
<tagNameFormat>wicket-@{project.version}</tagNameFormat>
<updateWorkingCopyVersions>false</updateWorkingCopyVersions>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Papache-release</arguments>
</configuration>
</plugin>
A couple of observations: up til our 6.12.0 release, the process
worked without a glitch. Since then I got a new laptop and have
migrated all settings to my new box.
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.
I am currently at a loss...
Does anyone have a solution?
Thanks,
Martijn
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Unable to use the maven-release-plugin to release
Posted by Martijn Dashorst <ma...@gmail.com>.
To fix this I had to add
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-gitexe</artifactId>
<version>1.9</version>
</dependency>
</dependencies>
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 <martijn.dashorst@gmail.com
> wrote:
> 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 <rf...@apache.org>wrote:
>
>> 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 schreef Julien Nicoulaud <
>> julien.nicoulaud@gmail.com>:
>>
>>
>> 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-ju-n-parent-pom/net-ju-n-parent-pom
>>>
>>> Cheers
>>>
>>>
>>> 2013/12/26 Mark Derricutt <ma...@talios.com>
>>>
>>> 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 that forces the use of
>>>> current scm-providers cause I can see this problem only increasing as
>>>> more
>>>> people a) upgrade git or b) move to git and get pissed off with
>>>> maven+git
>>>>
>>>> This work around works, but really - goes against convention over
>>>> configuration.
>>>>
>>>>
>>>> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>>>>
>>>> > 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
>>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: Unable to use the maven-release-plugin to release
Posted by Martijn Dashorst <ma...@gmail.com>.
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 <rf...@apache.org>wrote:
> 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 schreef Julien Nicoulaud <
> julien.nicoulaud@gmail.com>:
>
>
> 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-ju-n-parent-pom/net-ju-n-parent-pom
>>
>> Cheers
>>
>>
>> 2013/12/26 Mark Derricutt <ma...@talios.com>
>>
>> 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 that forces the use of
>>> current scm-providers cause I can see this problem only increasing as
>>> more
>>> people a) upgrade git or b) move to git and get pissed off with maven+git
>>>
>>> This work around works, but really - goes against convention over
>>> configuration.
>>>
>>>
>>> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>>>
>>> > 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
>>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: Unable to use the maven-release-plugin to release
Posted by Robert Scholte <rf...@apache.org>.
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 schreef Julien Nicoulaud
<ju...@gmail.com>:
> 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-ju-n-parent-pom/net-ju-n-parent-pom
>
> Cheers
>
>
> 2013/12/26 Mark Derricutt <ma...@talios.com>
>
>> 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 that forces the use of
>> current scm-providers cause I can see this problem only increasing as
>> more
>> people a) upgrade git or b) move to git and get pissed off with
>> maven+git
>>
>> This work around works, but really - goes against convention over
>> configuration.
>>
>>
>> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>>
>> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Unable to use the maven-release-plugin to release
Posted by Julien Nicoulaud <ju...@gmail.com>.
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-ju-n-parent-pom/net-ju-n-parent-pom
Cheers
2013/12/26 Mark Derricutt <ma...@talios.com>
> 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 that forces the use of
> current scm-providers cause I can see this problem only increasing as more
> people a) upgrade git or b) move to git and get pissed off with maven+git
>
> This work around works, but really - goes against convention over
> configuration.
>
>
> On 27 Dec 2013, at 1:43, Robert Scholte wrote:
>
> > 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
>
Re: Unable to use the maven-release-plugin to release
Posted by Mark Derricutt <ma...@talios.com>.
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 that forces the use of current scm-providers cause I can see this problem only increasing as more people a) upgrade git or b) move to git and get pissed off with maven+git
This work around works, but really - goes against convention over configuration.
On 27 Dec 2013, at 1:43, Robert Scholte wrote:
> 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
Re: Unable to use the maven-release-plugin to release
Posted by Robert Scholte <rf...@apache.org>.
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
<ma...@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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Unable to use the maven-release-plugin to release
Posted by Mark Derricutt <ma...@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.
RE: Unable to use the maven-release-plugin to release
Posted by Martin Gainty <mg...@hotmail.com>.
> 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: rfscholte@apache.org
>
> Hi,
MG>Guten Tag
>
> 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 have 2 options:
> - try maven-release-plugin 2.4
> - use an older version of GIT with English locale.
MG>Currently using GIT-1.8.5.2 ..which version GIT do you recommend?
MG>http://git-scm.com/download
MG>Frohe Weihnachten
MG>Martin-
> For details see https://jira.codehaus.org/browse/MRELEASE-812
>
> Robert
>
>
> Op Wed, 25 Dec 2013 13:28:26 +0100 schreef Martijn Dashorst
> <ma...@gmail.com>:
>
> > 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 that Maven fails to commit the updated release poms
> > and continues to tag and release the 6.13.0-SNAPSHOT versions.
> >
> > I have upgraded to maven 3.1.1, the release plugin runs at 2.4.2 and
> > our specified configuration is:
> >
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-release-plugin</artifactId>
> > <version>2.4.2</version>
> > <inherited>true</inherited>
> > <configuration>
> > <pushChanges>false</pushChanges>
> > <tagNameFormat>wicket-@{project.version}</tagNameFormat>
> > <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> > </configuration>
> > </plugin>
> >
> > When merged with the Apache parent pom (v10), this results in:
> >
> > <plugin>
> > <artifactId>maven-release-plugin</artifactId>
> > <version>2.4.2</version>
> > <inherited>true</inherited>
> > <configuration>
> > <pushChanges>false</pushChanges>
> > <tagNameFormat>wicket-@{project.version}</tagNameFormat>
> > <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> > <useReleaseProfile>false</useReleaseProfile>
> > <goals>deploy</goals>
> > <arguments>-Papache-release</arguments>
> > </configuration>
> > </plugin>
> >
> > A couple of observations: up til our 6.12.0 release, the process
> > worked without a glitch. Since then I got a new laptop and have
> > migrated all settings to my new box.
> >
> > 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.
> >
> > I am currently at a loss...
> >
> > Does anyone have a solution?
> >
> > Thanks,
> >
> > Martijn
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Unable to use the maven-release-plugin to release
Posted by Robert Scholte <rf...@apache.org>.
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 have 2 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 Wed, 25 Dec 2013 13:28:26 +0100 schreef Martijn Dashorst
<ma...@gmail.com>:
> 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 that Maven fails to commit the updated release poms
> and continues to tag and release the 6.13.0-SNAPSHOT versions.
>
> I have upgraded to maven 3.1.1, the release plugin runs at 2.4.2 and
> our specified configuration is:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.4.2</version>
> <inherited>true</inherited>
> <configuration>
> <pushChanges>false</pushChanges>
> <tagNameFormat>wicket-@{project.version}</tagNameFormat>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> </configuration>
> </plugin>
>
> When merged with the Apache parent pom (v10), this results in:
>
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.4.2</version>
> <inherited>true</inherited>
> <configuration>
> <pushChanges>false</pushChanges>
> <tagNameFormat>wicket-@{project.version}</tagNameFormat>
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> <useReleaseProfile>false</useReleaseProfile>
> <goals>deploy</goals>
> <arguments>-Papache-release</arguments>
> </configuration>
> </plugin>
>
> A couple of observations: up til our 6.12.0 release, the process
> worked without a glitch. Since then I got a new laptop and have
> migrated all settings to my new box.
>
> 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.
>
> I am currently at a loss...
>
> Does anyone have a solution?
>
> Thanks,
>
> Martijn
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org