[
http://jira.codehaus.org/browse/MRELEASE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Corneliussen updated MRELEASE-571:
---------------------------------------
Attachment: MRELEASE-571-collect-profiles.patch
Based on r983489 in https://svn.apache.org/repos/asf/maven/release/trunk
View Changes Online:
http://github.com/lcorneliussen/maven-release/compare/473197249e1caf39ee2cee6d0efc8a288c30d0c3...66439919ba7d2669e46db4cc7f88dd0d24b6709c
h4. Included commits:
- [MRELEASE-571] Active profiles for prepare and perform are now collected from
the current project and it's parents profiles (by Lars
Corneliussen<[email protected]> on 08.06.2010 13:44:10)
Created from
http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/tree/MRELEASE-571-collect-profiles
> 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,
> 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
