[ http://jira.jboss.com/jira/browse/JBIDE-1919?page=all ] Alexey Kazakov updated JBIDE-1919: ---------------------------------- Summary: If user renames any folder or project that we store in .settings/org.jboss.tools.seam.core.prefs then we should update proper properties. (was: If user rename any folder or project that we store in .settings/org.jboss.tools.seam.core.prefs then we should update proper properties.) Fix Version/s: 2.1 -- 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-1919?page=all ] Alexey Kazakov updated JBIDE-1919: ---------------------------------- Description: In my opinoin it's very useful to have such refactoring. For example we have .settings/org.jboss.tools.seam.core.prefs: action.package=org.domain.seamTestWAR.session action.sources=/seamTestWAR/src/action eclipse.preferences.version=1 model.package=org.domain.seamTestWAR.entity model.sources=/seamTestWAR/src/model seam.ejb.project=seamTestWAR seam.project.connection.profile=DefaultDS seam.project.deployment.type=war seam.project.settings.version=1.1 seam.project.web.root.folder=/seamTestWAR/WebContent seam.runtime.name=jboss-seam-2.0.0.GA seam.test.creating=false seam.test.project=seamTestWAR-test test.package=org.domain.seamTestWAR.test test.sources=/seamTestWAR-test/test-src So if we rename /seamTestWAR-test/test-src or /seamTestWAR/src/model or seamTestWAR or /seamTestWAR/WebContent or seamTestWAR-test we wiil get invalid seam properties for the project. It seems is not a big problem to solve it for 2.1. Max, should we do it? Testcases: EXECUTE: Create new seam ear project. EXECUTE: Rename ejb and test projects EXECUTE: Open <war seam project>/Properties/Seam Settings ASSERT: There is not any error on the page. EXECUTE: Rename war project EXECUTE: Open <ejb seam project>/Properties/Seam Settings ASSERT: There is not any error on the page. EXECUTE: Open <test seam project>/Properties/Seam Settings ASSERT: There is not any error on the page. EXECUTE: Rename <war seam project>/WebContent EXECUTE: Rename <ejb seam project>/ejbModule EXECUTE: Rename <test seam project>/test-src EXECUTE: Open <war seam project>/Properties/Seam Settings ASSERT: There is not any error on the page. EXECUTE: Rename org.domain.<projectname>.session package EXECUTE: Rename org.domain.<projectname>.entity package EXECUTE: Open <war seam project>/Properties/Seam Settings ASSERT: Model Package and Action Package properties equal the renamed packages. EXECUTE: Move <war seam project>/WebContent folder somewhere (but to the same project!) EXECUTE: Move <ejb seam project>/ejbModule folder somewhere (but to the same project!) EXECUTE: Move <test seam project>/test-src folder somewhere (but to the same project!) EXECUTE: Open <war seam project>/Properties/Seam Settings ASSERT: There is not any error on the page. was: In my opinoin it's very useful to have such refactoring. For example we have .settings/org.jboss.tools.seam.core.prefs: action.package=org.domain.seamTestWAR.session action.sources=/seamTestWAR/src/action eclipse.preferences.version=1 model.package=org.domain.seamTestWAR.entity model.sources=/seamTestWAR/src/model seam.ejb.project=seamTestWAR seam.project.connection.profile=DefaultDS seam.project.deployment.type=war seam.project.settings.version=1.1 seam.project.web.root.folder=/seamTestWAR/WebContent seam.runtime.name=jboss-seam-2.0.0.GA seam.test.creating=false seam.test.project=seamTestWAR-test test.package=org.domain.seamTestWAR.test test.sources=/seamTestWAR-test/test-src So if we rename /seamTestWAR-test/test-src or /seamTestWAR/src/model or seamTestWAR or /seamTestWAR/WebContent or seamTestWAR-test we wiil get invalid seam properties for the project. It seems is not a big problem to solve it for 2.1. Max, should we do it? -- 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-1919?page=all ] Denis Golovin updated JBIDE-1919: --------------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] -- 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