Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "FAQ How do I participate in a refactoring?"
m |
m |
||
| Line 1: | Line 1: | ||
| − | In Eclipse 3.0, the JDT introduced new API to allow | + | In Eclipse 3.0, the JDT introduced new API to allow other plug-ins to participate in simple refactorings. For example, if a user renames a method, JDT can fix up method references only in other standard Java files. If references to that method exist in Java-like files, such as JSPs, UML diagrams, or elsewhere, the plug-ins responsible for those files will want to update their references as well. |
| − | other plug-ins to participate in simple refactorings. For example, if a user | + | |
| − | renames a method, JDT can fix up method references only in other standard | + | |
| − | Java files. If references to that method exist in Java-like files, such as JSPs, | + | |
| − | UML diagrams, or elsewhere, the plug-ins responsible for those files will | + | |
| − | want to update their references as well. | + | |
| − | New extension points are defined by <tt>org.eclipse.jdt.ui</tt> | + | New extension points are defined by <tt>org.eclipse.jdt.ui</tt> for participation in renaming, creating, deleting, copying, and moving Java elements. The refactoring participant API is based on the new language-independent refactoring infrastructure in the LTK plug-ins. You can find more details by browsing through the extension point documentation for the new refactoring participant extension points. |
| − | for participation in renaming, creating, deleting, copying, and moving Java | + | |
| − | elements. The refactoring participant API is based on the new language-independent | + | |
| − | refactoring infrastructure in the LTK plug-ins. You can find more | + | |
| − | details by browsing through the extension point documentation for the new | + | |
| − | refactoring participant extension points. | + | |
== See Also: == | == See Also: == | ||
| − | *[[ | + | *[[FAQ What is LTK?]] |
| − | + | {{Template:FAQ_Tagline}} | |
Latest revision as of 23:42, 14 June 2006
In Eclipse 3.0, the JDT introduced new API to allow other plug-ins to participate in simple refactorings. For example, if a user renames a method, JDT can fix up method references only in other standard Java files. If references to that method exist in Java-like files, such as JSPs, UML diagrams, or elsewhere, the plug-ins responsible for those files will want to update their references as well.
New extension points are defined by org.eclipse.jdt.ui for participation in renaming, creating, deleting, copying, and moving Java elements. The refactoring participant API is based on the new language-independent refactoring infrastructure in the LTK plug-ins. You can find more details by browsing through the extension point documentation for the new refactoring participant extension points.
See Also:
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.