[jira] Commented: (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line

["Torsten Reinhard (JIRA)" <ji...@codehaus.org>]

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

Torsten Reinhard commented on MRELEASE-459:
-------------------------------------------

I ran into a comparable problem:
I´ve had a 'local' profile, which was activated by default. 
At mvn release:perform I want the profile 'release' to be activated - but what happened was that both profiles ('local' and 'release') were activated, trying to set the same variable.
My solution was, to remove the 'local' profile, which was activated by default before.

but then, at mvn release:perform no more profiles got activated:
[DEBUG] Executing: cmd.exe /X /C "C:\eap\apache-maven-2.2.1\bin\mvn.bat -X -D maven.repo.local=D:\mavenrepo -f maven-release-test -D performRelease=true deploy site-deploy"

=> So i now added a 'dummy' profile that is activated by default, but does nothing:
[DEBUG] Executing: cmd.exe /X /C "C:\eap\apache-maven-2.2.1\bin\mvn.bat -X -D maven.repo.local=D:\mavenrepo -f maven-release-test -D performRelease=true -P dummy,release deploy site-deploy"

using this workaround, I got my 'release' profile to work - after spending some hours with this issue....Please, fix that in one of the next releases or give a hint in the documentation.

Thanx, Torsten

> releaseProfiles has no effect without passing profiles in the command line 
> ---------------------------------------------------------------------------
>
>                 Key: MRELEASE-459
>                 URL: http://jira.codehaus.org/browse/MRELEASE-459
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.0-beta-8, 2.0-beta-9
>            Reporter: Andreas Christoforides
>         Attachments: patch.txt
>
>
> The releaseProfiles parameter on the perform goal is not taken into consideration when no other profiles are passed in the command line. In other words, the current code only uses the value of the parameter if you have additional profiles passed in. 
> Example:
> mvn release:perform -P someProfile (uses releaseProfiles value)
> mvn release:perform (does NOT use releaseProfiles value)
> The plugin should use the parameter even if no other profiles are passed. It should actually encourage release profiles configured in your POM as opposed to arbitrary profiles passed in the command line.
> I have included a patch that uses the releaseProfiles parameter regardless of any profiles passed in the command line.

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