You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Fabrizio Giudici (JIRA)" <ji...@codehaus.org> on 2011/07/14 23:39:42 UTC
[jira] Created: (MRELEASE-695) tagNameFormat with
@{project.version} tags the SNAPSHOT version
tagNameFormat with @{project.version} tags the SNAPSHOT version
---------------------------------------------------------------
Key: MRELEASE-695
URL: https://jira.codehaus.org/browse/MRELEASE-695
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Fabrizio Giudici
The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<localCheckout>true</localCheckout>
<preparationGoals>clean install verify</preparationGoals>
<goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
<arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
<tagNameFormat>@{project.version}</tagNameFormat>
</configuration>
</plugin>
but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-695) tagNameFormat with @{project.version} tags
the SNAPSHOT version
Posted by "Carlo de Wolf (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318358#comment-318358 ]
Carlo de Wolf commented on MRELEASE-695:
----------------------------------------
The variable is already resolved before {{InputVariablesPhase#execute}} gets a chance. So essentially the code that inserts {{releaseVersion}} and does an extra interpolate is moot.
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2
> Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <localCheckout>true</localCheckout>
> <preparationGoals>clean install verify</preparationGoals>
> <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
> <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
> <tagNameFormat>@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> {code}
> but I got the tag {{1.0-ALPHA-2-SNAPSHOT}} in place of {{1.0-ALPHA-2}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-695) tagNameFormat with
@{project.version} tags the SNAPSHOT version
Posted by "Aristedes Maniatis (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273811#comment-273811 ]
Aristedes Maniatis commented on MRELEASE-695:
---------------------------------------------
I can confirm. And I just wasted the last 3 hours of my life on this very simple bug. This makes the release plugin 2.2 very broken and almost useless for any regular user, since the tag created when you don't override tagNameFormat is incorrect. If you are re-using the same snapshot version (eg. 2.0b1 -> 2.0-SNAPSHOT -> 2.0b2 -> 2.0-SNAPSHOT) then everything breaks when the release cannot create the incorrect tag.
Downgrading to 2.1 solves the problem.
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <localCheckout>true</localCheckout>
> <preparationGoals>clean install verify</preparationGoals>
> <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
> <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
> <tagNameFormat>@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-695) tagNameFormat with @{project.version} tags
the SNAPSHOT version
Posted by "Duncan Jones (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320062#comment-320062 ]
Duncan Jones commented on MRELEASE-695:
---------------------------------------
I just encountered this bug on a recent project. However, having performed several successful releases on other projects in the past, I was intrigued why the issue has occurred. I had initially assumed it was because I moved to v2.4 and the other successfully tagged projects had used v2.2.1. However, when I enforced v2.2.1 on my failing project, the issue still occurred.
Rolling back to v2.1 solved the problem for me also. However, it does nothing to help explain why other projects have been tagged correctly using v2.2.1.
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2
> Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <localCheckout>true</localCheckout>
> <preparationGoals>clean install verify</preparationGoals>
> <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
> <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
> <tagNameFormat>@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> {code}
> but I got the tag {{1.0-ALPHA-2-SNAPSHOT}} in place of {{1.0-ALPHA-2}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-695) tagNameFormat with
@{project.version} tags the SNAPSHOT version
Posted by "Fabrizio Giudici (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273819#comment-273819 ]
Fabrizio Giudici commented on MRELEASE-695:
-------------------------------------------
BTW, I've downgraded to 2.1 as well. It's very unfortunate than a RFE which seems not to difficult to implement took almost 5 years to be implemented broken (just a consideration, not bashing anyone).
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <localCheckout>true</localCheckout>
> <preparationGoals>clean install verify</preparationGoals>
> <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
> <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
> <tagNameFormat>@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-695) tagNameFormat with @{project.version} tags
the SNAPSHOT version
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-695:
------------------------------------
Component/s: prepare
Description:
The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<localCheckout>true</localCheckout>
<preparationGoals>clean install verify</preparationGoals>
<goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
<arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
<tagNameFormat>@{project.version}</tagNameFormat>
</configuration>
</plugin>
{code}
but I got the tag {{1.0-ALPHA-2-SNAPSHOT}} in place of {{1.0-ALPHA-2}}.
was:
The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<localCheckout>true</localCheckout>
<preparationGoals>clean install verify</preparationGoals>
<goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
<arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
<tagNameFormat>@{project.version}</tagNameFormat>
</configuration>
</plugin>
but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---------------------------------------------------------------
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.2
> Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release with the following pom:
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <configuration>
> <localCheckout>true</localCheckout>
> <preparationGoals>clean install verify</preparationGoals>
> <goals>clean install javadoc:javadoc assembly:assembly deploy</goals>
> <arguments>-P${release.profiles} -DaltDeploymentRepository="${altDeploymentRepository}"</arguments>
> <tagNameFormat>@{project.version}</tagNameFormat>
> </configuration>
> </plugin>
> {code}
> but I got the tag {{1.0-ALPHA-2-SNAPSHOT}} in place of {{1.0-ALPHA-2}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira