You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andreas Christoforides (JIRA)" <ji...@codehaus.org> on 2009/07/13 10:52:22 UTC
[jira] Created: (MRELEASE-459) releaseProfiles has no effect
without passing profiles in the command line
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-9, 2.0-beta-8
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
RE: [jira] (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line
Posted by Wayne Seth <ws...@cox.net>.
Please remove me from this mailing list
Wayne Seth PMP CEA
(h) 520-459-8069
(c) 520-456-6169
http://www.wayneseth.com
-----Original Message-----
From: Robert Scholte (JIRA) [mailto:jira@codehaus.org]
Sent: Sunday, September 30, 2012 4:13 AM
To: issues@maven.apache.org
Subject: [jira] (MRELEASE-459) releaseProfiles has no effect
without passing profiles in the command line
[
https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlas
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-459.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in
[r1391992|http://svn.apache.org/viewvc?rev=1391992&view=rev]
> releaseProfiles has no effect without passing profiles in
the command
> line
>
------------------------------------------------------------
----------
> -----
>
> Key: MRELEASE-459
> URL:
https://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
> Assignee: Robert Scholte
> Labels: contributers-welcome, help-requested,
missing-integration-tests
> Fix For: 2.4
>
> Attachments: MRELEASE-459.1.patch, 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, please contact your
JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!defau
lt.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [jira] (MRELEASE-459) releaseProfiles has no effect without passing profiles in the command line
Posted by Wayne Seth <ws...@cox.net>.
Please remove me from this mailing list
Wayne Seth PMP CEA
(h) 520-459-8069
(c) 520-456-6169
http://www.wayneseth.com
-----Original Message-----
From: Robert Scholte (JIRA) [mailto:jira@codehaus.org]
Sent: Sunday, September 30, 2012 4:13 AM
To: issues@maven.apache.org
Subject: [jira] (MRELEASE-459) releaseProfiles has no effect
without passing profiles in the command line
[
https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlas
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-459.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in
[r1391992|http://svn.apache.org/viewvc?rev=1391992&view=rev]
> releaseProfiles has no effect without passing profiles in
the command
> line
>
------------------------------------------------------------
----------
> -----
>
> Key: MRELEASE-459
> URL:
https://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
> Assignee: Robert Scholte
> Labels: contributers-welcome, help-requested,
missing-integration-tests
> Fix For: 2.4
>
> Attachments: MRELEASE-459.1.patch, 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, please contact your
JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!defau
lt.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-459) releaseProfiles has no effect
without passing profiles in the command line
Posted by "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
[jira] Commented: (MRELEASE-459) releaseProfiles has no effect
without passing profiles in the command line
Posted by "Johan Walles (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213850#action_213850 ]
Johan Walles commented on MRELEASE-459:
---------------------------------------
Hi!
What remains to be done before this patch can be incorporated in the release plugin?
I just got hit by this and I'd really appreciate if this could be fixed.
Regards /Johan
> 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
[jira] (MRELEASE-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Martin Todorov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302591#comment-302591 ]
Martin Todorov edited comment on MRELEASE-459 at 7/3/12 7:32 AM:
-----------------------------------------------------------------
This works fine under version 2.2.2 of the plugin. I am actively using it. I think it can be closed.
was (Author: carlspring):
This works fine under version 2.2.2 of the plugin. I am actively using it.
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291036#comment-291036 ]
Stephen Connolly commented on MRELEASE-459:
-------------------------------------------
Needs some integration tests that fail before the patch is applied and pass after the patch is applied to:
1. prove there is an issue
2. prove the issue is fixed
3. prevent the issue from arising again.
I know this looks like a simple fix, but we really need integration tests to apply patches or quality will just decrease
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-459.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Robert Scholte
Fixed in [r1391992|http://svn.apache.org/viewvc?rev=1391992&view=rev]
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Assignee: Robert Scholte
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Fix For: 2.4
>
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect
without passing profiles in the command line
Posted by "Chris Watts (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283370#comment-283370 ]
Chris Watts commented on MRELEASE-459:
--------------------------------------
This also seems to effect maven3 maven-release-plugin:2.2.1
Not sure if it's to do with running maven thus:
mvn release:prepare release:perform
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302753#comment-302753 ]
Robert Scholte commented on MRELEASE-459:
-----------------------------------------
@Martin, it looks like the {{releaseProfiles}} are only passed when there's at least one other active profile, so it doesn't have to be a problem for everybody. Like Stephen already said before: first proof with an IT that this is still an issue.
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Lars Francke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Francke updated MRELEASE-459:
----------------------------------
Attachment: MRELEASE-459.1.patch
This is the exact same patch as before just created against the new directory layout.
All tests still pass.
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect
without passing profiles in the command line
Posted by "Dominic Mitchell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184721#action_184721 ]
Dominic Mitchell commented on MRELEASE-459:
-------------------------------------------
Just a pointer. I got caught out by this unexpectedly. It turned out that on one machine, I didn't have any profiles present in my {{settings.xml}}.
If you want to reproduce this, try temporarily moving your {{settings.xml}} out of the way.
> 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
[jira] (MRELEASE-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Lars Francke (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291038#comment-291038 ]
Lars Francke commented on MRELEASE-459:
---------------------------------------
Thanks for the comment and the explanation.
If no one else jumps on it before I'll try to provide an updated patch but I can't commit to a date yet. Need to understand how ITs work here first, too.
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Martin Todorov (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302591#comment-302591 ]
Martin Todorov commented on MRELEASE-459:
-----------------------------------------
This works fine under version 2.2.2 of the plugin. I am actively using it.
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect
without passing profiles in the command line
Posted by "Karl M. Davis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218807#action_218807 ]
Karl M. Davis commented on MRELEASE-459:
----------------------------------------
I actually had to use the following to get things to work:
{{mvn release:perform -Darguments="-PmyProfileToActivate"}}
I think this is because I'm also using the {{-DconnectionUrl=...}} option and don't have any profiles defined in my {{settings.xml}}.
> 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
[jira] (MRELEASE-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306397#comment-306397 ]
Andrei Pozolotin commented on MRELEASE-459:
-------------------------------------------
fyi: this is still a problem as of 2.3.2;
hey, this soon will make it into a book of records! :-)
it will be named: "the curse of the maven release plugin"
http://stackoverflow.com/questions/3291938/maven-release-plugin-ignores-releaseprofile
workaround is still the same: put a dummy profile in settings.xml
{code:title=settings.xml|borderStyle=solid}
<profiles>
<profile>
<id>default</id>
</profile>
</profiles>
<activeProfiles>
<activeProfile>default</activeProfile>
</activeProfiles>
{code}
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Attachments: MRELEASE-459.1.patch, 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, 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-459) releaseProfiles has no effect without passing
profiles in the command line
Posted by "Andrei Pozolotin (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310325#comment-310325 ]
Andrei Pozolotin commented on MRELEASE-459:
-------------------------------------------
thank you!
> releaseProfiles has no effect without passing profiles in the command line
> ---------------------------------------------------------------------------
>
> Key: MRELEASE-459
> URL: https://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
> Assignee: Robert Scholte
> Labels: contributers-welcome, help-requested, missing-integration-tests
> Fix For: 2.4
>
> Attachments: MRELEASE-459.1.patch, 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, 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