Bug 333691 - Add support for multiple javadocs per Jar
Summary: Add support for multiple javadocs per Jar
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-06 15:15 EST by Glenview Jeff CLA
Modified: 2011-04-23 06:50 EDT (History)
4 users (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 Glenview Jeff CLA 2011-01-06 15:15:02 EST 
Build Identifier: M20100909-0800

Others and I have a need for adding more than one javadoc per jar file in Eclipse.  From Stackoverflow.com:

While this may sound strange, I want to be able to attach more than one JavaDoc location to the same JAR in an Eclipse project. This particular JAR has classes from two sets of JavaDoc. The reason for this is that it is an OSGi bundle, which consists of a third-party JAR, and some other third-party code on top of that JAR to make it work in OSGi.

If I have the source code to both packages, and have that source code in an Eclipse project, it works fine. But I'd like to be able to get this to work in the case that I just have the JARs and JavaDoc.

Reproducible: Always
Comment 1 Ayushman Jain CLA 2011-01-07 01:06:20 EST 
Olivier, what's your take on this?
Comment 2 Olivier Thomann CLA 2011-01-07 08:31:00 EST 
Jay, please investigate what would need to be done.
Comment 3 Jay Arthanareeswaran CLA 2011-01-10 10:14:22 EST 
While I am doing investigation on possible API breakage and changes, I am copying Markus also since it would involve UI changes as well.
Comment 4 Markus Keller CLA 2011-01-11 10:22:37 EST 
See also bug 173641 (asks for multiple source attachments).
Comment 5 Stanimir Stamenkov CLA 2011-04-23 06:50:11 EDT 
It would be nice if javadoc locations could be specified globally per package / package hierarchy (and possibly overridden for project).  This way one would not need to attach javadoc location to every jar which possibly implement and include certain APIs.  This would be especially useful for Java EE APIs.