You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugen Paraschiv (JIRA)" <ji...@codehaus.org> on 2011/07/02 00:17:42 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=272101#comment-272101 ]
Eugen Paraschiv commented on MRELEASE-571:
------------------------------------------
Does this account for:
http://stackoverflow.com/questions/3987983/maven-release-plugin-with-profile-dependent-submodules
?
Thanks.
> 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.3
>
> 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