| Summary: | [DOM] should getModifiers() of a IPackageBinding be deprecated if package-info.java file is deprecated? | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | kent_johnson, markus.kell.r, martinae |
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Olivier Thomann
Martin, What would you expect in this case? Wouldn't that mean that we also have to set this bit in the Java model world (IPackageFragment)? I don't know what happens in the UI when suddenly packages can be deprecated. I definitely sounds useful, but if we do it, we should coordinate the effort and we also need to be consistent in search/Java model and AST bindings. As of Java 7, a package-info.java cannot be deprecated. 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. |