Bug 366044 - Building Javadoc for multiple projects
Summary: Building Javadoc for multiple projects
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 09:34 EST by Thorsten Meinl CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

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 Thorsten Meinl CLA 2011-12-08 09:34:39 EST 
Build Identifier: M20110210-1200

Currently it is hard if not impossible to build a combined Javadoc for multiple projects with Buckminster. The ideal scenario would be to define a feature (or any other component), defined some dependencies and then build a combined Javadoc for all the dependencies.
Currently there are several issues that make it hard to do it with existing BM concepts:
- components do not expose their source paths publicly. It is only available in the private eclipse.build.source attribute.
- components do not expose their required libraries (the classpath for the javadoc invocation) publicly. It is only available in the private attributes java.binaries and bin.includes.

One crude way would be to traverse the dependency tree programmtically (e.g. by means of an actor) and collect all required attributes and then build an appropriate Javadoc call. However, I couldn't find a way to traverse the tree and even then there should be something built in.

Reproducible: Always