Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <20316635.1233939079789.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Fri, 6 Feb 2009 10:51:19 -0600 (CST)
From: "Wendy Smoak (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-1504) when autoVersionSubmodules=true
 is defined in the pom for the release plugin, the release prepare screen
 should not show or allow changing of child project versions
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/CONTINUUM-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=164262#action_164262 ] 

Wendy Smoak commented on CONTINUUM-1504:
----------------------------------------

What is the expected behavior after this change?

I tried it at r741440 with examples/mm-example in the sandbox, which has 'autoVersionSubmodules' set to true, and I still see it prompting for a version for both mm-parent _and_ the mm-core submodule.

Here's the project:
http://svn.apache.org/repos/asf/continuum/sandbox/examples/mm-example/

This Selenium test shows the steps I used:
http://svn.apache.org/repos/asf/continuum/trunk/continuum-webapp-test/src/test/selenium-ide/test_release_plugin_configuration.html

(It's possible that Continuum isn't reading correctly from the pom -- I don't see the comment prefix show up on the release prepare page either.  See CONTINUUM-2028 and CONTINUUM-2054)

> when autoVersionSubmodules=true is defined in the pom for the release plugin, the release prepare screen should not show or allow changing of child project versions
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1504
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1504
>             Project: Continuum
>          Issue Type: Bug
>          Components: Release
>    Affects Versions: 1.1-beta-3
>            Reporter: Tomislav Stojcevich
>            Assignee: Emmanuel Venisse
>             Fix For: 1.3.2
>
>
> 90% of the time the defaults for the versions are correct, however when I need to use a different value i have to make the change in too many places on the screen.  when using the release plugin, it only asks me for the parent versions and propgates them down automatically.  i would assume the release prepare screen would do the same and not have inputs available to put in child pom versions.

-- 
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