[
http://jira.codehaus.org/browse/CONTINUUM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219405#action_219405
]
Wendy Smoak commented on CONTINUUM-2512:
----------------------------------------
A workaround is to move the release plugin config to <plugins> (instead of
<pluginManagement>).
> Continuum ignores release plugin configuration in pluginManagement section
> --------------------------------------------------------------------------
>
> Key: CONTINUUM-2512
> URL: http://jira.codehaus.org/browse/CONTINUUM-2512
> Project: Continuum
> Issue Type: Bug
> Affects Versions: 1.4.1 (Beta)
> Environment: Continuum
> Version: 1.4.1-SNAPSHOT
> Build Number: 939301
> Reporter: Wendy Smoak
> Priority: Minor
> Attachments: continuum-ignores-release-config-in-plugin-mgmt.png
>
>
> When using Continuum Release, Continuum ignores release plugin configuration
> in <pluginManagement>.
> It should pick up any release plugin configuration in the pom and default it
> into the Release Prepare form.
> See the example project at
> http://svn.apache.org/repos/asf/continuum/sandbox/examples/release-config-test/
> To reproduce,
> 1. add this project to Continuum,
> 2. build it,
> 3. click Release
> 4. choose Prepare Release and click submit
> Because autoVersionSubmodules is set to true, there should only be one set of
> prompts for the version for the parent project. Instead, you see it prompt
> for both the parent and child module. (see screen shot)
--
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
