10:04 p.m.
Add refactoring capability to Java parser
-----------------------------------------
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
10:04 p.m.
New subject: [JBoss JIRA] Updated: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Dan Allen updated SEAMFORGE-172:
--------------------------------
Summary: Add refactoring capability to code manipulator (was: Add refactoring
capability to Java parser)
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
10:52 p.m.
New subject: [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
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
6:59 p.m.
New subject: [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on SEAMFORGE-172:
-----------------------------------------------
This would require you to be an omnipotent IDE - I really don't think this is worth
the effort compared to getting some good extendible reverse engineering/scaffolding
going.
But that said, yes Eclipse does this based on AST; but you might be going into the plugins
that requires osgi to actually run.
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
7:21 p.m.
New subject: [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
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
9:03 p.m.
New subject: [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Dan Allen commented on SEAMFORGE-172:
-------------------------------------
{quote}
I think we should probably provide minimal in-project refactoring support
{quote}
Agreed, the scope is in-project. I'm not suggesting that we match the functionality
and scope an IDE provides. But refactoring is essential to being able to intelligently
manipulate the project.
{quote}
I don't think this should be a priority for us since we are encouraging use of Forge +
IDE of choice.
{quote}
I think it should be a medium priority. The priority is for the plugins, not necessarily
for providing top-level refactoring commands. Plugins will often need to effectively do a
refactoring, and without that control, the plugin will have to hack and slash...which is
what we want to be able to avoid.
To make my position clear, I do still see this as a complement to and IDE.
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
8:46 a.m.
New subject: [JBoss JIRA] Commented: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Koen Aers commented on SEAMFORGE-172:
-------------------------------------
What would be relatively easy to do is to add an 'Eclipse-specific' refactoring
plugin that is included in the Forge-Eclipse integration. For Forge this would basically
be a noop that delegates to the Eclipse refactoring functionality. Of course this
won't help people that use other IDEs.
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
11:21 p.m.
New subject: [JBoss JIRA] Updated: (SEAMFORGE-172) Add refactoring capability to code manipulator
[
https://issues.jboss.org/browse/SEAMFORGE-172?page=com.atlassian.jira.plu...
]
Lincoln Baxter III updated SEAMFORGE-172:
-----------------------------------------
Priority: Optional (was: Major)
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
Priority: Optional
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
4705
days inactive
4727
days old
7 comments
5 participants
participants (5)
-
Dan Allen (JIRA) -
Koen Aers (JIRA)
-
Lincoln Baxter III (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Paul Bakker (JIRA)