| commit | cc687aa53456a6211f191da39dd3b04107316a77 | [log] [tgz] |
|---|---|---|
| author | Jeff Johnston <jjohnstn@redhat.com> | Mon May 28 18:49:55 2018 -0400 |
| committer | Kalyan Prasad Tatavarthi <kalyan_prasad@in.ibm.com> | Wed Jul 04 04:33:23 2018 -0400 |
| tree | 68708a5d8d70459bcb10e707afe3ee3bf0ccfa3c | |
| parent | f49f45c8f9f2047db09e89802fa658a0b50d589c [diff] |
Bug 535242 - Refactor CompilationUnitRewriteOperationsFix - split CompilationUnitRewriteOperationsFix into CompilationUnitRewriteOperationsFixCore in jdt.core.manipulation and have CompilationUnitRewriteOperationsFix extend it and implement ILinkedFix - move AbstractFix, and IProposableFix as well, but change IProposableFix to depend on new ICleanUpFixCore class (essentially copy of ICleanUpFix) - create a core version of ILinkedFix called ILinkedFixCore in jdt.core.manipulation and have AbstractFix refer to it instead of ILinkedFix - create new ICleanUpFixCore and ICleanUpCore interfaces to be used in place of ICleanUpFix and ICleanUp public interfaces - move CompilationUnitChange, CompilationUnitRewrite, ContextSensitiveImportRewriteContext, FixMessages, ImportRemover, RedundantNullnessTypeAnnotationsFilter, RefactoringASTParser, and RefactoringCoreMessages - split CleanUpConstants into two classes: CleanUpConstants which resides in jdt.core.manipulation and only contains static constant values and CleanUpConstantsOptions which extends CleanUpConstants and implements methods that manipulate the IPreferenceStore - copy CleanUpRequirements, CleanUpOptions, and CleanUpContext to jdt.core.manipulation/corext and have the jdt.ui public versions use an instance of their internal counterpart to perform the logic - modify the various users of above classes in jdt.ui Change-Id: Iaf63c45d282c6902bc230a56bbad590bea66bb47 Signed-off-by: Jeff Johnston <jjohnstn@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.