Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364842 - Issue with Javadoc/ JavaDoc needs testing
Summary: Issue with Javadoc/ JavaDoc needs testing
Status: CLOSED INVALID
Alias: None
Product: GMF-Tooling
Classification: Modeling
Component: Releng (show other bugs)
Version: 2.4   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-25 09:36 EST by Mickael Istria CLA
Modified: 2012-12-08 09:29 EST (History)
1 user (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 Mickael Istria CLA 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 CLA 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 CLA 2012-12-08 09:29:37 EST 
We don't use Javadoc any more, See bug 396056