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

Bug 338488

Summary: API Use Reports scan location requires "xml" parent directory
Product: [Eclipse Project] PDE Reporter: Peter Parapounsky <pjparapo>
Component: API ToolsAssignee: Ankur Sharma <ankur_sharma>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, pjparapo
Version: 3.7   
Target Milestone: 3.7 M7   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Peter Parapounsky CLA 2011-02-28 18:19:06 EST 
Build Identifier: eclipse-SDK-I20110222-0800-win32.zip

The "API Use Scans" preference allows adding API use scans so they can be compared to the workspace to ensure the API references still exist. I ran into the following problem when I tried it out. My scan report location was accepted as valid in the preference page dialog. However, the API analysis builder didn't report the errors I expected it to report. I spend some time trying to figure why. Eventually, I looked into the source code and found out that at run time, the "UseScanManager.getExactScanLocation()" method looks for a parent "xml" directory and if this directory is not there, it silently interrupts the scan so there is not way to figure out why it didn't produce the expected results. 
I don't understand why is there a requirement the scan report's parent directory to be named "xml". And second, if this is a needed requirement, I think there should be a prominent error displayed, and probably at the time the location is added and validated.

Reproducible: Always
Comment 1 Curtis Windatt CLA 2011-03-01 13:41:25 EST 
Ankur, please investigate as soon as possible.  Would this also affect the new use scan task?
Comment 2 Ankur Sharma CLA 2011-04-18 17:47:24 EDT 

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