Bugzilla – Full Text Bug Listing
| Summary: | Add cleanup action for using static import | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | fabrice.tiercelin, gautier.desaintmartinlacaze, Lars.Vogel |
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| See Also: | https://git.eclipse.org/r/125335 | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 197850 | ||
| Bug Blocks: | |||
|
Description
Lars Vogel
Fabian, please provide a Gerrit for providing a cleanup action for the conversion to static imports. Should it be possible to trigger this cleanup only for method invocations or only for variable/constant access (QualifiedName)? (In reply to Fabian Pfaff from comment #2) > Should it be possible to trigger this cleanup only for method invocations or > only for variable/constant access (QualifiedName)? I think it would be "nice-to-have" to have two options, something like: [ ] Use static imports - [X] For static method invocations - [X] For static field access While X indicates the suggested default values. New Gerrit change created: https://git.eclipse.org/r/125335 New Gerrit change created: https://git.eclipse.org/r/125335 Fabrice, can you take this one over? This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |