You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brent N Atkinson (JIRA)" <ji...@codehaus.org> on 2015/04/02 00:07:18 UTC

[jira] (CONTINUUM-2512) Continuum ignores release plugin configuration in pluginManagement section

    [ https://jira.codehaus.org/browse/CONTINUUM-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365984#comment-365984 ] 

Brent N Atkinson commented on CONTINUUM-2512:
---------------------------------------------

Should confirm if this still occurs after CONTINUUM-2094 was addressed.

> Continuum ignores release plugin configuration in pluginManagement section
> --------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2512
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2512
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: Continuum
> Version:	 1.4.1-SNAPSHOT
> Build Number:	 939301
>            Reporter: Wendy Smoak
>            Priority: Minor
>              Labels: backlog-to-cleanup
>         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 was sent by Atlassian JIRA
(v6.1.6#6162)