Community
Participate
Working Groups
When associating Javadoc to a library, there is no way to make a relative association. All associations are either URLs to local or remote resources, or "Javdoc in archive" which also captures an absolute path. "Javadoc in archive" even captures an absolute path when the Javadoc archive is located in the workspace. This prevents teams from sharing projects files that make reference to Javadoc for 3rd party libs that live within the project's workspace, unless all team members use the same drive/directory layout. Additionally, there is no way to extend a variable (like one can with source) for Javadoc. It's desirable is some situations to store the source and Javadoc with the 3rd party libraries within the project. The team can all share the benefits of navigating source and documentation without having to maintain it individually, and without having to actively hit the internet for public documentation. Regards, Christian
*** Bug 213366 has been marked as a duplicate of this bug. ***
*** Bug 122805 has been marked as a duplicate of this bug. ***
This is an example of the problem using JUnit in 4.2.2. The library itself and the source jar are put in .classpath using project-relative paths, but the javadoc jar path is workspace relative and includes a hard coded project name: <classpath> <classpathentry kind="src" path="src"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.7"/> <classpathentry kind="lib" path="lib/junit-4.11.jar" sourcepath="lib/junit-4.11-sources.jar"> <attributes> <attribute name="javadoc_location" value="jar:platform:/resource/MyProject/lib/junit-4.11-javadoc.jar!/"/> </attributes> </classpathentry> <classpathentry kind="output" path="bin"/> </classpath>
We have the same problem. We are using junit and have a shared project, that ppl named differently.
I would be grateful if someone would finally take care of the problem (unfortunately, I can't).
