Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 328964

Summary: jsdt.doc needs retagging
Product: [WebTools] JSDT Reporter: David Williams <david_williams>
Component: GeneralAssignee: Nitin Dahyabhai <thatnitind>
Status: RESOLVED FIXED QA Contact: Nitin Dahyabhai <thatnitind>
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: 3.3 M4   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description David Williams CLA 2010-10-28 14:42:40 EDT
In a recent "comparator report" for an I-build, it was reported that the jsdt.doc bundle had same version tag as a previous build, but 4 extra files. 

On build machine's shell, I unzipped the jars to a temp location, did some diffs, and found the current bundle contains these 4 additional files: 

Only in wstsdk//reference/api/org/eclipse/wst/jsdt/debug/core/jsdi/event/class-use: ResumeEvent.html
Only in wstsdk//reference/api/org/eclipse/wst/jsdt/debug/core/jsdi/event: ResumeEvent.html
Only in wstsdk//reference/api/org/eclipse/wst/jsdt/debug/core/jsdi/request/class-use: ResumeRequest.html
Only in wstsdk//reference/api/org/eclipse/wst/jsdt/debug/core/jsdi/request: ResumeRequest.html

I know next to nothing about JavaDoc generation, but assume this happens because the Platform's JavaDoc changed? Or is there some subtle issues with the way we create JavaDoc? 

In either case, more minor than if there was a "code difference". So up to you of when you want to fix ... for a respin now, or for just for final M3 ... but would see the project needs to be re-tagged, in order to have unique version for unique contents.
Comment 1 Nitin Dahyabhai CLA 2010-10-28 14:57:00 EDT
Will tag after today's build is declared.
Comment 2 Nitin Dahyabhai CLA 2010-11-05 16:53:20 EDT
tagged