[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Lincoln Baxter III commented on SEAMFORGE-172:
----------------------------------------------
Refactoring using the eclipse plugins would require that we boot the eclipse runtime in
memory, start a workspace, and use that to track all of our file changes. While this
*could* be done, I really don't think that should be our job. Forge is not designed to
handle that kind of functionality, since refactoring often reaches beyond the single
project. Eclipse and other IDE's are much better at this. I think we should probably
provide minimal in-project refactoring support, and forego the more complex stuff.
I don't think this should be a priority for us since we are encouraging use of Forge +
IDE of choice.
Add refactoring capability to code manipulator
----------------------------------------------
Key: SEAMFORGE-172
URL:
https://issues.jboss.org/browse/SEAMFORGE-172
Project: Seam Forge
Issue Type: Feature Request
Components: Parsers / File Manipulation
Affects Versions: 1.0.0.Alpha3
Reporter: Dan Allen
Although challenging, the ability to refactor within a project would be immensely
powerful for plugin writers. Basic refactoring include renaming types, fields and methods.
Matching updates to resource files (XML, Java properties, etc) would also be useful. We
could see how far that could take us before deciding if more complex refactoring is
necessary.
I would suggest researching whether it's possible to extra the refactoring logic out
of the Eclipse tooling into a reusable library (if it isn't already). Another option
is RefactorIT, which used to be a proprietary plugin for the major Java IDEs but is now
CDDL and GPL:
http://sourceforge.net/projects/refactorit/
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira