Bug 129175 - [jres] Don't set Javadoc location path if there isn't any Javadoc
Summary: [jres] Don't set Javadoc location path if there isn't any Javadoc
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 129168
  Show dependency tree
 
Reported: 2006-02-23 11:02 EST by Dani Megert CLA
Modified: 2009-08-30 02:15 EDT (History)
1 user (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 Dani Megert CLA 2006-02-23 11:02:07 EST 
3.2 M5

The Javadoc location path shouldn't be set if there isn't any Javadoc.
Comment 1 Darin Wright CLA 2006-05-01 18:26:39 EDT 
Deferred
Comment 2 Dani Megert CLA 2006-06-16 10:45:23 EDT 
Can this be addressed for 3.3? Note that it is also a performance issue.
Comment 3 Darin Wright CLA 2006-06-16 10:50:27 EDT 
Yes, we aim to please...
Comment 4 Darin Wright CLA 2007-02-27 17:49:55 EST 
We might be able to leverage the OSGi execution environment access rules to determine which packages have javadoc/source (i.e. list of API packages). The current API on execution environments does not expose what we would need to do this, but we could do something internally, since the EE implementation and the 'standard vm type' are both in the launching plug-in.
Comment 5 Darin Wright CLA 2007-04-17 09:33:51 EDT 
Not planned for 3.3 - I'm afraid this would impact launching performance. Each time we launch a JRE with default libraries, the default libraries are computed. This includes the computaion of javadoc locations. We would need to examine the contents of each library to see how it matches with the API of the system library, which would be slow. The information could be cached - but then we run the risk of becoming incosistent with the file system.

(I know later is deprecated, but for now that is our style of marking bugs for future consideration).
Comment 6 Denis Roy CLA 2009-08-30 02:15:53 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.