maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-667) Profiles activated in settings.xml can't be deactivated for release
Date Tue, 04 Dec 2012 21:41:14 GMT

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

Robert Scholte closed MRELEASE-667.
-----------------------------------

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

Fixed with MRELEASE-592, added an IT in [r1417200|http://svn.apache.org/viewvc?rev=1417200&view=rev]
                
> Profiles activated in settings.xml can't be deactivated for release
> -------------------------------------------------------------------
>
>                 Key: MRELEASE-667
>                 URL: https://jira.codehaus.org/browse/MRELEASE-667
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform, prepare
>    Affects Versions: 2.1
>         Environment: Maven 2.2.1
>            Reporter: Michael Hinterseher
>            Assignee: Robert Scholte
>             Fix For: 2.4
>
>
> We are having a development profile in settings.xml to sign the jars.
> For releases the release profile shall be used to sign with an official key.
> I can't convince the release plugin to deactivate the development profile active as default
in settings.xml
> I tried various combinations but nothing works:
> - specify profiles configuration: <arguments>-Prelease,!development</arguments>
> - specify profiles configuration: <releaseProfiles>release,!development</releaseProfiles>

> - adding -Darguments="-Prelease,!development" -Prelease,!development release:prepare
> - adding -Darguments="-Prelease,!development" -Prelease,!development release:perform
> - combinations of the above
> Running deploy with "-Prelease,!development" uses the correct profile and signs with
the correct key.
> It looks like the disabled properties are not propagated to the actual build but just
removed and then inherited from settings.xml again.
> This affects both the release:prepare and the release:perform

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

        

Mime
View raw message