| Summary: | Plugin Import could set JavadocLocation | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Martin Aeschlimann <martinae> |
| Component: | UI | Assignee: | Wassim Melhem <wassim.melhem> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, ed.burnette |
| Version: | 1.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Martin Aeschlimann
Cannot be contained in 2.1 because it requires us to reverse-engineer mapping between a Jar and a location in the documentation. There is no reliable 1-1 mapping - we would need to guess and make assumptions based on doc organization that is not API. Please reope this bug. Just had 2 other request for this feature on the jdt newsgroup. So far we have two isv doc plugins, and you could use a heuristic to map plugins the isv plugins. The problem is that its almost impossible to config the locations from hand, too many plugins so configure. If the source for a jar (including a plug-in jar) is available then the Javadoc is automatically available and there is no need to set a Javadoc location - jdt pulls it from the source comments. Just hover the mouse over a method/class/etc., or press F2 for a bigger window. Reopening... Doing it by hand is pretty tedious. Tons of JARs. We might be able to use the org.eclipse.pde.source extension point to help map plugins to Javadoc locations. *** This bug has been marked as a duplicate of 52894 *** |