[ http://jira.jboss.com/jira/browse/JBIDE-991?page=all ] Aliaksey Nis updated JBIDE-991: ------------------------------- Affects Version/s: 2.0.0.Beta2 Assignee: (was: Aliaksey Nis) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-991?page=comments#action_12382108 ] Victor Rubezhny commented on JBIDE-991: --------------------------------------- This validation isn't fixed as far as I know. +1 for this issue -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-991?page=comments#action_12382357 ] Denis Golovin commented on JBIDE-991: ------------------------------------- if there are projects for seamprojectname-ear, seamprojectname-war, seamprojectname-test, we can show an error that some projects that should be created already exist and doesn't allow go next. Is that what expected? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-991?page=comments#action_12382405 ] Victor Rubezhny commented on JBIDE-991: --------------------------------------- Validation of what page should care of project folders duplication? We can't make the user not to go next from the first page, because ear or war project is selected on the last page (if we disable "next" button at first page the user never can change project type). Also we can't predict what type of project (which is to be selected on the last page) to make decision: to validate for *-ear and *-ejb projects duplication or not. So, IMHO, the correct place to do this validation is the last page. But the user will have to rewind to the first page to change the project name in case of possible project duplications. It's not good at all but better than if we require the user to change project name on the first page while *-ejb or *-ear project exists and user want to select war-project. I think it will be good to create additional page which will give the possibility to change names for *-test, *-ejb and *-ear projects in case of names duplication. (Probably not for GA) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-991?page=all ] Victor Rubezhny resolved JBIDE-991. ----------------------------------- Resolution: Done Test Case: EXECUTE: Create a new seam project deployed as EAR. Name it "Test" for example. ASSERT: See that four projects are created ("Test", "Test-test", "Test-ear", "Test-ejb") EXECUTE: Remove project "Test" from the workspace. (Another three projects are still in the workspace.) EXECUTE: Run again the Seam Project Wizard and try to create project with the same name ("Test" in our example), leave all the wizard fields unchanged and press "Next" button untill the last page ("Seam Facet"). ASSERT: See an error message: "Test project 'Test-test' already exists....". "Finish" button is disabled. EXECUTE: Exit wizard and remove "Test-test" project from the workspace. EXECUTE: Run again the Seam Project Wizard and try to create project with the same name ("Test" in our example), leave all the wizard fields unchanged and press "Next" button untill the last page ("Seam Facet"). EXECUTE: Set the value of "Deploy as" combo to "ear". ASSERT: See an error message: "EAR project 'Test-ear' already exists....". "Finish" button is disabled. EXECUTE: Change the value of "Deploy as" combo to "war". ASSERT: See no error messages in the title. "Finish" button is enabled. EXECUTE: Exit wizard and remove "Test-ear" project from the workspace. EXECUTE: Run again the Seam Project Wizard and try to create project with the same name ("Test" in our example), leave all the wizard fields unchanged and press "Next" button untill the last page ("Seam Facet"). EXECUTE: Set the value of "Deploy as" combo to "ear". ASSERT: See an error message: "EJB project 'Test-ejb' already exists....". "Finish" button is disabled. EXECUTE: Change the value of "Deploy as" combo to "war". ASSERT: See no error messages in the title. "Finish" button is enabled. EXECUTE: Exit wizard and remove "Test-ejb" project from the workspace. EXECUTE: Run again the Seam Project Wizard and try to create project with the same name ("Test" in our example), leave all the wizard fields unchanged and press "Next" button untill the last page ("Seam Facet"). ASSERT: See no error messages in the title. "Finish" button is enabled. EXECUTE: Change the value of "Deploy as" combo to "war" and back again to "ear". ASSERT: See no error messages appear in the title. "Finish" button is enabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira