You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ion Iovu (JIRA)" <ji...@codehaus.org> on 2010/11/30 16:00:03 UTC

[jira] Created: (MRELEASE-623) unexpected mvn release:prepare behavior for project with 2.2-SNAPshot

unexpected mvn release:prepare behavior for project with <version>2.2-SNAPshot</version>
----------------------------------------------------------------------------------------

                 Key: MRELEASE-623
                 URL: http://jira.codehaus.org/browse/MRELEASE-623
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
    Affects Versions: 2.1
         Environment: Windows XP
C:\>java -version
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
            Reporter: Ion Iovu
            Priority: Minor
         Attachments: pom.xml

While running mvn release:prepare on a project with 
<version>2.2-SNAPSHOT</version> the goal executes successfully, as expected.

On a project with
<version>2.2</version> the goal fails as expected, because it's not a snapshot.

However, on a project with
<version>...-SNAPshot</version> the goal doesn't fail, i.e. the project is considered a snapshot.

In interactive mode the proposed defaults are:

Actual results:

release version: 2.2-SNAPshot
SCM release tag or label: myproject-2.2-SNAPshot
new development version: myproject-2.2-SNAPshot-SNAPSHOT

Conclusion: the version label is not treated as that of a snapshot project

Expected results:
Either:
a) if SNAPSHOT is not in upper-case the goal treats the project as a release, therefore fails.
b) the proposed defaults becom:
release version: 2.2
SCM release tag or label: myproject-2.2
new development version: myproject-2.2-SNAPSHOT


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] (MRELEASE-623) unexpected mvn release:prepare behavior for project with 2.2-SNAPshot

Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRELEASE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-623.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3
         Assignee: Robert Scholte

Fixed in [rev. 1296476|http://svn.apache.org/viewvc?rev=1296476&view=rev]
{{DefaultVersionInfo}} doesn't use its own implementation of {{isSnapshot()}} anymore, but uses {{ArtifactUtils.isSnapshot(String)}}.
Tested with both Maven-2.2.1 and Maven 3.0.4
                
> unexpected mvn release:prepare behavior for project with <version>2.2-SNAPshot</version>
> ----------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-623
>                 URL: https://jira.codehaus.org/browse/MRELEASE-623
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>         Environment: Windows XP
> C:\>java -version
> java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
> Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
>            Reporter: Ion Iovu
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 2.2.3
>
>         Attachments: pom.xml
>
>
> While running mvn release:prepare on a project with 
> <version>2.2-SNAPSHOT</version> the goal executes successfully, as expected.
> On a project with
> <version>2.2</version> the goal fails as expected, because it's not a snapshot.
> However, on a project with
> <version>...-SNAPshot</version> the goal doesn't fail, i.e. the project is considered a snapshot.
> In interactive mode the proposed defaults are:
> Actual results:
> release version: 2.2-SNAPshot
> SCM release tag or label: myproject-2.2-SNAPshot
> new development version: myproject-2.2-SNAPshot-SNAPSHOT
> Conclusion: the version label is not treated as that of a snapshot project
> Expected results:
> Either:
> a) if SNAPSHOT is not in upper-case the goal treats the project as a release, therefore fails.
> b) the proposed defaults becom:
> release version: 2.2
> SCM release tag or label: myproject-2.2
> new development version: myproject-2.2-SNAPSHOT

--
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] (MRELEASE-623) unexpected mvn release:prepare behavior for project with 2.2-SNAPshot

Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRELEASE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated MRELEASE-623:
------------------------------------

    Component/s: prepare
    
> unexpected mvn release:prepare behavior for project with <version>2.2-SNAPshot</version>
> ----------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-623
>                 URL: https://jira.codehaus.org/browse/MRELEASE-623
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.1
>         Environment: Windows XP
> C:\>java -version
> java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
> Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
>            Reporter: Ion Iovu
>            Priority: Minor
>         Attachments: pom.xml
>
>
> While running mvn release:prepare on a project with 
> <version>2.2-SNAPSHOT</version> the goal executes successfully, as expected.
> On a project with
> <version>2.2</version> the goal fails as expected, because it's not a snapshot.
> However, on a project with
> <version>...-SNAPshot</version> the goal doesn't fail, i.e. the project is considered a snapshot.
> In interactive mode the proposed defaults are:
> Actual results:
> release version: 2.2-SNAPshot
> SCM release tag or label: myproject-2.2-SNAPshot
> new development version: myproject-2.2-SNAPshot-SNAPSHOT
> Conclusion: the version label is not treated as that of a snapshot project
> Expected results:
> Either:
> a) if SNAPSHOT is not in upper-case the goal treats the project as a release, therefore fails.
> b) the proposed defaults becom:
> release version: 2.2
> SCM release tag or label: myproject-2.2
> new development version: myproject-2.2-SNAPSHOT

--
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