[
http://jira.codehaus.org/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116416
]
Scott Rankin commented on MRELEASE-294:
---------------------------------------
I've encountered the same problem. It's because in the
GenerateReleasePomsPhase#createReleasePlugins, for some reason, it's only
getting the original plugin list from the child pom, excluding any
configuration from the super pom. I've got a patch for this that I will attach
that seems to work for me.
> Generated release-pom.xml does not contain plugins configured in a super pom.
> -----------------------------------------------------------------------------
>
> Key: MRELEASE-294
> URL: http://jira.codehaus.org/browse/MRELEASE-294
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Reporter: Reinhard Nägele
> Attachments: patch.txt
>
>
> Finally, since 2.0-beta-6 it has been possible to generate release poms.
> Unfortunately, plugins configured in a super pom don't make it into the
> {{release-pom.xml}}.
> We have a multi-module project. Each module inherits from a super pom that
> also defines the modules. The super pom, amongst others, configures the
> compiler plugin for {{source}} and {{target 1.5}}. Since these plugin
> configurations only make it into the release pom of the super pom, but not
> into the release poms of the modules, the modules fail to build using the
> release plugin.
> {{generics are not supported in -source 1.3 (try -source 1.5 to enable
> generics)}}
> {{annotations are not supported in -source 1.3 (try -source 1.5 to enable
> annotations) @Override}}
> So, we still have to set {{generateReleasePoms}} to {{false}}.
--
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
