You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lars Corneliussen (JIRA)" <ji...@codehaus.org> on 2010/06/08 13:39:12 UTC
[jira] Created: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
When collecting active profiles, the active profiles from parent poms are not considered
----------------------------------------------------------------------------------------
Key: MRELEASE-571
URL: http://jira.codehaus.org/browse/MRELEASE-571
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: perform, prepare
Affects Versions: 2.0
Reporter: Lars Corneliussen
MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-571:
--------------------------------------
Fix Version/s: (was: 2.3)
2.2.1
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2.1
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-571) When collecting active
profiles, the active profiles from parent poms are not considered
Posted by "Georges-Etienne Legendre (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257039#action_257039 ]
Georges-Etienne Legendre edited comment on MRELEASE-571 at 2/21/11 8:36 AM:
----------------------------------------------------------------------------
A workaround is to define the -Dargument option:
{noformat}PROFILES="foo1,foo2,ignored"
mvn -P$PROFILES -Darguments="-P$PROFILES" release:prepare
{noformat}
was (Author: legege):
A workaround is to define the -Dargument option:
{noformat}
PROFILES="foo1,foo2,ignored"
mvn -P$PROFILES -Darguments="-P$PROFILES" release:prepare
{noformat}
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Issue Comment Edited: (MRELEASE-571) When collecting active
profiles, the active profiles from parent poms are not considered
Posted by "Georges-Etienne Legendre (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257038#action_257038 ]
Georges-Etienne Legendre edited comment on MRELEASE-571 at 2/21/11 8:29 AM:
----------------------------------------------------------------------------
Here is a test case that reproduces this problem. If you execute "mvn -Pfoo1,foo2,ignored release:prepare", the release plugin ends up with only the "foo1" and "foo2" profiles.
Tested with Maven 2.2.1 and 3.0.2. Same results.
was (Author: legege):
Here is a test case that reproduces this problem. If you execute "mvn -Pfoo1,foo2,ignored release:prepare", the release plugin ends up with only the "foo1" and "foo2" profiles.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRELEASE-571:
----------------------------------
Fix Version/s: (was: 2.1)
2.2
could you add a test or integration test for this? This would help verify it is fixed, and also compare results between Maven 2.2.1 and Maven 3.0 where the profile collection may have changed.
It's also best to leave formatting changes out of the patch :)
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-571:
--------------------------------------
Fix Version/s: (was: 2.2.1)
2.3
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.3
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-571) When collecting active profiles, the active
profiles from parent poms are not considered
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-571.
-----------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fixed in [r1391856|http://svn.apache.org/viewvc?rev=1391856&view=rev]
Be aware that this fix will only work for Maven3, because only this version has an API to get the original passed commandline arguments.
To get the same result with Maven2 requires a lot of calculations and even then it is not sure if all profiles are gathered.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> {{MavenProject.getActiveProfiles()}} does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Issue Comment Edited: (MRELEASE-571) When collecting active
profiles, the active profiles from parent poms are not considered
Posted by "Eugen Paraschiv (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272101#comment-272101 ]
Eugen Paraschiv edited comment on MRELEASE-571 at 7/1/11 5:19 PM:
------------------------------------------------------------------
Does this account for:
http://stackoverflow.com/questions/3987983/maven-release-plugin-with-profile-dependent-submodules
?
If it does not, then I can file a bug for that problem.
Thanks.
was (Author: eugenparaschiv):
Does this account for:
http://stackoverflow.com/questions/3987983/maven-release-plugin-with-profile-dependent-submodules
?
Thanks.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.3
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-571) When collecting active profiles,
the active profiles from parent poms are not considered
Posted by "Eugen Paraschiv (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272101#comment-272101 ]
Eugen Paraschiv commented on MRELEASE-571:
------------------------------------------
Does this account for:
http://stackoverflow.com/questions/3987983/maven-release-plugin-with-profile-dependent-submodules
?
Thanks.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.3
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-571) When collecting active profiles, the active
profiles from parent poms are not considered
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-571:
------------------------------------
Description:
{{MavenProject.getActiveProfiles()}} does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
This leads to preparation-builds of modules without the specified active profiles derived from their parents.
was:
MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
This leads to preparation-builds of modules without the specified active profiles derived from their parents.
Fix Version/s: (was: 2.3)
2.4
Pushing this to 2.4
I think there's only one clean solution: passing the original profile arguments and not the ones calculated as being the active profiles.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.4
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> {{MavenProject.getActiveProfiles()}} does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-571:
---------------------------------------
Attachment: MRELEASE-571-collect-profiles.patch
Based on r983489 in https://svn.apache.org/repos/asf/maven/release/trunk
View Changes Online: http://github.com/lcorneliussen/maven-release/compare/473197249e1caf39ee2cee6d0efc8a288c30d0c3...66439919ba7d2669e46db4cc7f88dd0d24b6709c
h4. Included commits:
- [MRELEASE-571] Active profiles for prepare and perform are now collected from the current project and it's parents profiles (by Lars Corneliussen<me...@lcorneliussen.de> on 08.06.2010 13:44:10)
Created from http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/tree/MRELEASE-571-collect-profiles
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-571:
---------------------------------------
Attachment: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch
GIT-Patch with the following changes: http://github.com/lcorneliussen/maven-release/commit/89d9799a56d46d7435d08c94ca538845d7145c9b
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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-571) When collecting active profiles,
the active profiles from parent poms are not considered
Posted by "Georges-Etienne Legendre (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=257039#action_257039 ]
Georges-Etienne Legendre commented on MRELEASE-571:
---------------------------------------------------
A workaround is to define the -Dargument option:
{noformat}
PROFILES="foo1,foo2,ignored"
mvn -P$PROFILES -Darguments="-P$PROFILES" release:prepare
{noformat}
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-571:
--------------------------------------
Fix Version/s: (was: 2.2)
2.3
Pushing back from target of 2.2 to 2.3 as:
1. Patch includes formatting changes.
2. Patch does not include any integration test.
3. No summary of testing results of this patch against 2.2.1 and 3.0.x to check for regression with the different profile activation mechanism between 2.x and 3.x
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: https://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.3
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRELEASE-571:
----------------------------------
Fix Version/s: 2.1
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.1
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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] Updated: (MRELEASE-571) When collecting active profiles, the
active profiles from parent poms are not considered
Posted by "Georges-Etienne Legendre (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Georges-Etienne Legendre updated MRELEASE-571:
----------------------------------------------
Attachment: profile-ignored-with-module.zip
Here is a test case that reproduces this problem. If you execute "mvn -Pfoo1,foo2,ignored release:prepare", the release plugin ends up with only the "foo1" and "foo2" profiles.
> When collecting active profiles, the active profiles from parent poms are not considered
> ----------------------------------------------------------------------------------------
>
> Key: MRELEASE-571
> URL: http://jira.codehaus.org/browse/MRELEASE-571
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform, prepare
> Affects Versions: 2.0
> Reporter: Lars Corneliussen
> Fix For: 2.2
>
> Attachments: 89d9799a56d46d7435d08c94ca538845d7145c9b[1].patch, MRELEASE-571-collect-profiles.patch, profile-ignored-with-module.zip
>
>
> MavenProject.getActiveProfiles() does not return all profiles that are currently run, but instead only those that are run AND defined on the current project.
> This leads to preparation-builds of modules without the specified active profiles derived from their parents.
--
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