commit | 111134180351538364d0ad9a6f3fbb24a22fe481 | [log] [tgz] |
---|---|---|
author | Jeff Johnston <jjohnstn@redhat.com> | Thu Nov 04 18:20:17 2021 -0400 |
committer | Jeff Johnston <jjohnstn@redhat.com> | Fri Nov 05 21:35:20 2021 -0400 |
tree | bd022c762dbd7dd074a270eb9c1b778911192a5e | |
parent | 005b8c51ea6aa87095ba6d8097bf177cbf3030ab [diff] |
Bug 566949 - Pattern Instanceof Source->Surround with try-catch error - add getVariableBindings() method to SurroundWithTryCatchAnalyzer that finds variables referenced by selected code and cover PatternInstanceofExpression nodes - add findNodesInRange() method logic from SurroundWithTryWithResources refactoring to SurroundWithTryCatchRefactoring which finds all affected nodes by surrounding selected range and uses new getVariableBindings() from analyzer - move any nodes in range that are not already selected inside the resultant try/catch statement - add new SurroundWithTests16 class and add this to AllTests Change-Id: I96cccb60eeeecf404133af87f9f6f01815eca5fe Reviewed-on: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/187364 Tested-by: JDT Bot <jdt-bot@eclipse.org> Tested-by: Jeff Johnston <jjohnstn@redhat.com> Reviewed-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.