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

["Sander Verhagen (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170574#action_170574 ] 

Sander Verhagen edited comment on MRELEASE-294 at 3/22/09 3:24 PM:
-------------------------------------------------------------------

There is more missing from the release-pom generation to make it useful. Transitive exclusions get forgotten, see the actual example below, which has been causing me problems. Perhaps this is a little different issue, but I can't find this problem as a separate JIRA-issue, so we could well tag it along with this one, can't we?

Here is the example:

- My POM is dependent on hibernate-entitymanager
- hibernate-entitymanager is dependent on jboss-common-core, while excluding e.g. jboss-common-logging-spi
- My generated release POM is dependent on hibernate-entitymanager (good), jboss-common-core (fair enough)
- The dependency on jboss-common-core leads to a dependency on jboss-common-logging-spi (undesired per the original exclusion)

If anyone knows a workaround for this, or can me point into a direction for building a patch, I'd be much obliged.

      was (Author: sverhagen):
    There is more missing from the release-pom generation to make it useful. Transitive exclusions get forgotten, see the actual example below, which has been causing me problems. Perhaps this is a little different issue, but I can't find this problem as a separate JIRA-issue, so we could well tag it along with this one, can't we?

Here is the example:

- My POM is dependent on hibernate-entitymanager
- hibernate-entitymanager is dependent on jboss-common-core, while excluding e.g. jboss-common-logging-spi
- My generated release POM is dependent on hibernate-entitymanager (good), jboss-common-core (fair enough)
- The dependency on jboss-common-core leads to a dependency on jboss-common-logging-spi (undesired per the original exclusion)
  
> 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
>          Components: prepare
>    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