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]
