You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/09/15 14:34:32 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 ]
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