Quantcast

[jira] Created: (MRELEASE-356) depreate the automated release profile

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Created: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org
depreate the automated release profile
--------------------------------------

                 Key: MRELEASE-356
                 URL: http://jira.codehaus.org/browse/MRELEASE-356
             Project: Maven 2.x Release Plugin
          Issue Type: Task
            Reporter: Brett Porter


the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Commented: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138968#action_138968 ]

Chris Maki commented on MRELEASE-356:
-------------------------------------

Will the release plugin still set the property -DperformRelease=true?  In the plugin documentation for the release goal, there is an optional parameter, arguments, but it seems this is ignored by the release goal.  If you take away the release profile, please keep the performRelease=true property or make arguments work :-)

Given this plugin definition:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-release-plugin</artifactId>
        <version>2.0-beta-7</version>
        <configuration>
          <arguments>-Pprofile-name</arguments>
        </configuration>
      </plugin>

The release goal has this output:

[INFO] Executing: mvn deploy --no-plugin-updates -DperformRelease=true -f pom.xml

Note there is no -Pprofile-name in the resulting mvn sub-command.

> depreate the automated release profile
> --------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>            Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] Updated: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Heritier updated MRELEASE-356:
-------------------------------------

    Component/s: perform

> depreate the automated release profile
> --------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Commented: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195677#action_195677 ]

Mark Hobson commented on MRELEASE-356:
--------------------------------------

Is this still the case?  It's still there in the super POM for 2.2.x.

> depreate the automated release profile
> --------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Commented: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221499#action_221499 ]

Peter Lynch commented on MRELEASE-356:
--------------------------------------

Can someone include a link here to a mailing list discussion or similar that states that the release profile will be removed or modified in an upcoming Maven release, 3.x or otherwise?

> depreate the automated release profile
> --------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Commented: (MRELEASE-356) depreate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221554#action_221554 ]

Brett Porter commented on MRELEASE-356:
---------------------------------------

it appears to have been added back in Maven 3 as well, but still with the deprecation note. Probably would be changed for Maven 3.1 so that it can be tied to the POM model version.

> depreate the automated release profile
> --------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Updated: (MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRELEASE-356:
----------------------------------

    Fix Version/s: 2.1
          Summary: deprecate the automated release profile  (was: depreate the automated release profile)

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.1
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Updated: (MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRELEASE-356:
----------------------------------

    Fix Version/s:     (was: 2.1)
                   2.2

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: http://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.2
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Updated: (MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ https://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Connolly updated MRELEASE-356:
--------------------------------------

    Fix Version/s:     (was: 2.2)
                   2.3

Punting to 2.3 as not critical now that the release profile is back in 3.0

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: https://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.3
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Commented: (MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ https://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282454#comment-282454 ]

Karl M. Davis commented on MRELEASE-356:
----------------------------------------

Stephen: I hadn't heard that it's back in 3.0. Do you know of any documentation I can read regarding this?

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: https://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.3
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

(MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ https://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated MRELEASE-356:
------------------------------------

    Fix Version/s:     (was: 2.3)
                   2.4
   

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: https://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.4
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

(MRELEASE-356) deprecate the automated release profile

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ https://jira.codehaus.org/browse/MRELEASE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=307530#comment-307530 ]

Anders Hammar commented on MRELEASE-356:
----------------------------------------

Karl: It's there, check the super-POM (note the comment though): http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml?view=markup
               

> deprecate the automated release profile
> ---------------------------------------
>
>                 Key: MRELEASE-356
>                 URL: https://jira.codehaus.org/browse/MRELEASE-356
>             Project: Maven 2.x Release Plugin
>          Issue Type: Task
>          Components: perform
>            Reporter: Brett Porter
>             Fix For: 2.4
>
>
> the release profile is being removed from the super POM in Maven 2.1-alpha-1, so the release plugin should pre-emptively start ensuring users do this themselves

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

       
Loading...