maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRELEASE-571) When collecting active profiles, the active profiles from parent poms are not considered
Date Wed, 29 Sep 2010 14:29:34 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated MRELEASE-571:
----------------------------------

    Fix Version/s:     (was: 2.1)
                   2.2

could you add a test or integration test for this? This would help verify it is fixed, and
also compare results between Maven 2.2.1 and Maven 3.0 where the profile collection may have
changed.

It's also best to leave formatting changes out of the patch :)

> 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.2
>
>         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

        

Mime
View raw message