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

Bug 364842

Summary:	Issue with Javadoc/ JavaDoc needs testing
Product:	[Modeling] GMF-Tooling	Reporter:	Mickael Istria <mistria>
Component:	Releng	Assignee:	Project Inbox <gmp.gmf-tooling-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	blocker
Priority:	P3	CC:	borlander
Version:	2.4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mickael Istria

2011-11-25 09:36:55 EST

Since we generate JavaDoc in the Tycho build as part of a "generate-resource" step, that means that we have a dependency on BUILT artifacts during first build. So on a clean Maven repo, build fails because artifacts do not exist yet to generate JavaDoc.

Some improvements in CI jobs configuration at hudson.eclipse.org made these jobs failing.

I´ll work on using a profile for Javadoc, so that Javadoc could be disabled when necessary. However, this is a source of mistakes, we'll need to be very careful with it (write a Unit test?) to ensure "real" builds will contain JavaDoc.

Comment 1 Mickael Istria

2011-11-25 11:01:39 EST

Builds seem to be back on rail. I let this bug open in order to provide a Unit test verifying the contribution of Javadoc.

Comment 2 Mickael Istria

2012-12-08 09:29:37 EST

We don't use Javadoc any more, See bug 396056