You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/28 16:29:43 UTC

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

     [ 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