[
http://jira.jboss.com/jira/browse/JBIDE-1919?page=comments#action_12403290 ]
Max Andersen commented on JBIDE-1919:
-------------------------------------
yes, sounds definitly like a good thing. we have done if for the hibernate launch configs
wiht the irenameparticipants etc. which integrates nice into eclipse refactoring.
If user rename any folder or project that we store in
.settings/org.jboss.tools.seam.core.prefs then we should update proper properties.
----------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-1919
URL:
http://jira.jboss.com/jira/browse/JBIDE-1919
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Seam
Affects Versions: 2.0.1, 2.1
Reporter: Alexey Kazakov
Assigned To: Alexey Kazakov
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