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:47:12 UTC

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

     [ 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