Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366044

Summary:	Building Javadoc for multiple projects
Product:	z_Archived	Reporter:	Thorsten Meinl <thorsten>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Thorsten Meinl

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