You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:50:15 UTC
[jira] (MRELEASE-610) release-pom.xml does not contain plugins
versions
[ https://jira.codehaus.org/browse/MRELEASE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRELEASE-610.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> release-pom.xml does not contain plugins versions
> -------------------------------------------------
>
> Key: MRELEASE-610
> URL: https://jira.codehaus.org/browse/MRELEASE-610
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Danar Barzanji
>
> I've a parent POM (PP), in which my plugins have been managed and configured. When I want to generate a release-pom.xml file for a project, which its parent the mentioned Parent Pom (PP), the release-pom.xml file will not use the pre-configuration from parent pom. In the other hand the effective pom uses the plugin configuration from parent pom.
> For example: I've defined maven-compiler plugin, which uses JDK 1.6, in my Parent POM. The generated release-pom.xml files still uses jdk 1.3, which causes Exception during compilation
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)