Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 96747 - Cannot specify javadoc location for .jars under Plug-in Dependecies
Summary: Cannot specify javadoc location for .jars under Plug-in Dependecies
Status: RESOLVED DUPLICATE of bug 52894
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-26 03:55 EDT by Claus Nielsen CLA
Modified: 2005-07-04 20:57 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claus Nielsen CLA 2005-05-26 03:55:56 EDT
After upgrading to Eclipse 3.1M7 (and the matching MyEclipse version) I can
no longer specify javadoc location for the .jars under Plug-in Dependencies.
In
the previous version (M4 was the last one I used), I believe I simply right-clicked
the .jar, selected Properties and then Java Doc Location. This still works for
other .jars (the JRE jars for example), but for the .jars under Plugin dependencies,
I get a message telling me that javadoc location can only be attached to Java
projects or archives and class folders in Java projects.

Do I specify the
javadoc location somewhere else, or is something broken?

Oh, and by the way.
since the javadoc is included in the Eclipse distribution, someone really ought
to do something about getting the javadoc locations configured, so that it just
works out-of-the-box :-)
Maby someone already started doing that - hover javadoc
seems to be working, but external javadoc (via Ctrl-F2) does not.
Comment 1 Mike Kaufman CLA 2005-06-20 16:07:11 EDT
This bug needs to be in the "Core" component.  I don't have privs to update 
the bug.  Claus, can you move the Component to "Core"? 

Thanks!
Comment 2 Claus Nielsen CLA 2005-06-21 01:38:26 EDT
Moved to core as reqested.
Comment 3 Dirk Baeumer CLA 2005-07-04 09:45:15 EDT
Class path entries for referenced plug-ins are managed by the PDE class path
container. Since the container is marked as read-only, we can't set the Javadoc
locations from outside anymore (note that storing Javadoc locations as class
path attributes got introduced in 3.1).

Moving to PDE. To get this working again PDE has to support modification of
class path attributes or has to autodetect the Javadoc and add provide this
attribite for the generated class path entries.
Comment 4 Wassim Melhem CLA 2005-07-04 20:57:02 EDT

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