[
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
