| Summary: | Organize import with constant on package private class triggers compilation error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jean-Noel Rouvignac <djanoiup> | ||||
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Manoj N Palat <manoj.palat> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jarthana, manoj.palat | ||||
| Version: | 4.7.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Jean-Noel Rouvignac
The problem lies in `org.eclipse.jdt.core.dom.rewrite.ImportRewrite.addStaticImport(IBinding)` which blindly adds the import to `addedImports` collection as "fullyQualifiedNameOfDeclaringClass.fieldName" without checking whether the declaring class (`PackagePrivate`) is accessible from the current code (`OrganizeImportTriggersCompileError`). (In reply to Jean-Noel Rouvignac from comment #1) > The problem lies in > `org.eclipse.jdt.core.dom.rewrite.ImportRewrite.addStaticImport(IBinding)` I am not an expert in this area, but the analysis reasoning sounds plausible. Would you be able to put that in patch, preferably with a test case? TIA! 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. |