Summary: | [compiler] Incremental compile confuses unsound type hierarchy and deprecation | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> | ||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | major | ||||||
Priority: | P3 | CC: | kent_johnson, Olivier_Thomann | ||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 M6 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Philipe Mulet
2006-02-24 06:41:56 EST
Likely a consequence of our new support for unsound type hierarchies, which is getting a bit collision with deprecated modifier. Indeed: on ClassFileConstants int AccHierarchyInconsistent = ASTNode.Bit22; on ExtraCompilerModifiers final int AccDeprecatedImplicitly = ASTNode.Bit22; // record whether deprecated itself or contained by a deprecated type Changed classfile modifiers to be a tagbit. Created attachment 35296 [details]
Patch changing the offending modifier into a tagbit
Kent/Olivier : pls add a builder test for this I will release my changes soon after the tests complete. Fixed. Regression test still needed. Added regression test: org.eclipse.jdt.core.tests.builder.IncrementalTests.test129316 Verified for 3.2 M6 using build I20060327-0010 |