[jira] (MRELEASE-571) When collecting active profiles, the active profiles from parent poms are not considered

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