Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364749 - Many test failures in Maintenance builds when using 1.5/1.6
Summary: Many test failures in Maintenance builds when using 1.5/1.6
Status: CLOSED DUPLICATE of bug 365132
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.8 M4   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 14:39 EST by Curtis Windatt CLA
Modified: 2011-11-29 15:42 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2011-11-24 14:39:12 EST 
http://download.eclipse.org/eclipse/downloads/drops/M20111123-0800/testresults/html/org.eclipse.pde.api.tools.tests_macosx.cocoa.x86_5.0.html

Problem : Tag '@noextend' is unsupported on an enum field [ resource : </tagproject/src/a/b/c/test5.java> range : <910,919> category : <-1> severity : <2>]
Problem : Tag '@noextend' is unsupported on a private enum field [ resource : </tagproject/src/a/b/c/test5.java> range : <961,970> category : <-1> severity : <2>]
and many more...

Reproducible locally.
Comment 1 Curtis Windatt CLA 2011-11-25 17:09:47 EST 
When the incremental builder runs, each problem is reported multiple times (in most cases 5 times, making 4 become 20 problems, but locally it repeated 6 times).  If a full build is run or a clean+build, the correct number of problems are reported.

There are no changes in API Tools to account for the change.

I will try debugging through the builder on Monday with Mike.
Comment 2 Curtis Windatt CLA 2011-11-25 17:18:18 EST 
Also, it looks like test classes that have only a single expected problem are passing.  Those that have multiple problems (tags on methods, fields, inner classes, etc.) fail with repeated problem markers.
Comment 3 Curtis Windatt CLA 2011-11-29 15:42:38 EST 
In September, a change in JDT core caused problems with the builder reading member types multiple times (the same compilation unit would be returned and analyzed for each member type).  The JDT fix was backported last week, but the corresponding API Tools fix was never marked for backport.

*** This bug has been marked as a duplicate of bug 365132 ***