[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator

[Paul Bakker (JIRA)]

    [ https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602688#comment-12602688 ] 

Paul Bakker commented on SEAMFORGE-172:
---------------------------------------

I wonder how Eclipse handle it's refactorings. Wouldn't that be on the AST level? In that case we could maybe use that directly.

> 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