[
http://jira.codehaus.org/browse/CONTINUUM-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157747#action_157747
]
Wendy Smoak commented on CONTINUUM-1953:
----------------------------------------
I can't test this on trunk because on the Build Definition Template page, the
arrows to move build defs from the 'available' to 'used' area are not working.
I did reproduce it on the 1.2 branch as mentioned on Oct 31 with the following
Selenium IDE test:
http://svn.apache.org/repos/asf/continuum/branches/continuum-1.2.x/continuum-webapp-test/src/test/selenium-ide/test_build_definition_templates.html
> [regression] Build definitions not linked when creating a new project with a
> given build defintion template
> -----------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1953
> URL: http://jira.codehaus.org/browse/CONTINUUM-1953
> Project: Continuum
> Issue Type: Bug
> Components: Web - Configuration
> Affects Versions: 1.2
> Environment: Linux / Java 1.6.0_10 / mvn 2.0.9
> Reporter: Jean-Paul GUIGUI
> Fix For: 1.2.3
>
>
> When adding a new Maven2 project with the Web interface, I'm associating the
> project with a given BuildDefinitionTemplate.
> The project is created but no build definition is associated to the project.
> I need to associate all the build definitions of the template manually to the
> project.
> It looks like the function
> AddMavenProjectAction.setBuildDefinitionTemplateId() is never called.
> I have migrated from Continuum 1.1 to 1.2 . It used to work in previous
> version.
--
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
