[jira] [Commented] (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.

["Bruno Marti (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533435#comment-16533435 ] 

Bruno Marti commented on MRELEASE-294:
--------------------------------------

problem still exists in version 2.5.3.

Why not using help:effective-pom to generate release-pom.xml?

I would really appreciate this feature(y)

> Generated release-pom.xml does not contain plugins configured in a super pom.
> -----------------------------------------------------------------------------
>
>                 Key: MRELEASE-294
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-294
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare-with-pom
>    Affects Versions: 2.0-beta-6
>            Reporter: Reinhard Nägele
>            Priority: Major
>         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 was sent by Atlassian JIRA
(v7.6.3#76005)