> To: [email protected]
> Subject: Re: Unable to use the maven-release-plugin to release
> Date: Wed, 25 Dec 2013 13:46:43 +0100
> From: [email protected]
>
> 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
> <[email protected]>:
>
> > 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: [email protected]
> > For additional commands, e-mail: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
