[
http://jira.codehaus.org/browse/MRELEASE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246246#action_246246
]
Christoph Kutzinski commented on MRELEASE-415:
----------------------------------------------
We had an unusable release because of that and it took us roughly 1 day to find
out the reason for this.
Given that there is a patch which fixes the problem, could someone please apply
it?
> Plugin fails to activate profiles in submodules.
> ------------------------------------------------
>
> Key: MRELEASE-415
> URL: http://jira.codehaus.org/browse/MRELEASE-415
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0-beta-8
> Environment: Fedora8, Sun Java 1.6.0_07, Maven 2.0.9
> Reporter: David C. Hicks
> Attachments: AbstractReleaseMojo.patch
>
>
> (I hope this is not a duplicate. I searched JIRA but didn't find anything
> that looked like one.)
> In a multi-module project, profiles that are activated only for sub-modules
> (not the parent project) are omitted from execution during release:perform.
> In my specific case, I have a large, multi-module project in which one of the
> sub-modules is there to create an assembly during release. Since I only want
> it to run during release, I've placed that into a profile in the sub-module's
> pom.xml. When I run release:perform, I activate the profile. However, the
> profile is never executed.
> Workaround: By adding a dummy profile to the parent pom.xml, I was able to
> get release:perform to operate as desired.
> I'm afraid I don't have an example to upload, at this time. If I can find
> the time, I'll try to create one and come back to upload it.
--
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
