| commit | c32d1ac2887b37b6a556a64253de84126fda6778 | [log] [tgz] |
|---|---|---|
| author | Jeff Johnston <jjohnstn@redhat.com> | Wed Jan 30 15:50:48 2019 -0500 |
| committer | Roland Grunberg <rgrunber@redhat.com> | Fri Apr 26 15:13:21 2019 -0400 |
| tree | 68a07bec7d0dba5607771f580415dab09bcaf941 | |
| parent | 70ae9b8106fc817baa844ba0cfda9f93d049f718 [diff] |
Bug 543991 - Refactor CallHierarchy and associated classes for jdt.ls - create new package org.eclipse.jdt.internal.corext.callhierarchy in jdt.core.manipulation and make it visible to jdt.ui - create new IMethodWrapperDynamic interface that defines equals() and getAdapter() methods that can be used to substitute for the ones in MethodWrapper - move MethodWrapper to java.core.manipulation and add a static IMethodWrapperDynamic instance variable that is used by the equals() and getAdapter() methods - create a MethodWrapperDynamic class in jdt.ui that implements IMethodWrapperDynamic and defines equals() and getAdapter() methods that access IWorkbenchAdapter and MethodWrapperWorkbenchAdapter classes that are unavailable in jdt.core.manipulation - create a MethodWrapperDynamicCore class that is similar but does not refer to the workbench classes - initialize the static IMethodWrapperDynamic instance in MethodWrapper in JavaPlugin - refactor CalleeAnalyzerVisitor, CalleeMethodWrapper, CallerMethodWrapper, CallHierarchyMessages, CallHierarchyVisitor, CallLocation, CallSearchResultCollector, IImplementorFinder, Implementors, JavaImplementorFinder, MethodCall, MethodReferencesSearchRequestor, and RealCallers to jdt.core.manipulation - create CallHierarchyCore in jdt.core.manipulation based on CallHierarchy - change CallHierarchy to get an instance of CallHierarchyCore to use in various methods that don't use preference store - refactor StringMatcher to jdt.core.manipulation Change-Id: I716251700d785ce806e1b425fed7a01aba6b11b9 Signed-off-by: Jeff Johnston <jjohnstn@redhat.com> Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
Thanks for your interest in this project.
The JDT UI implements the user interface for the Java IDE. This includes views like Package Explorer and JUnit, the Java and properties files editors, Java search, and refactorings. Website: http://www.eclipse.org/jdt/ui/
Contributions to JDT UI are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
Public forum for Eclipse JDT users.
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.