You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/05/06 20:58:00 UTC

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

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

Slawomir Jaranowski commented on MRELEASE-294:
----------------------------------------------

Please retest with the latest version on plugin and Maven.

> 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
(v8.20.7#820007)