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

Bug 370384

Summary:	jetty-distribution is dependent on jetty-all aggregate?
Product:	[RT] Jetty	Reporter:	Greg Wilkins <gregw>
Component:	server	Assignee:	Jesse McConnell <jesse.mcconnell>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	jesse.mcconnell, jetty-inbox
Version:	8.1.0
Target Milestone:	7.5.x
Hardware:	All
OS:	All
Whiteboard:

Description Greg Wilkins

2012-02-01 20:26:08 EST

The jetty-distribution is dependent on the jetty-all aggregate.  This should not be the case because the aggregates are really just other distributions (and I'd really like to remove them from the normal build).

More importantly, the jetty-all javadoc jar is ending up in the distro lib directory, which is just 4.5MB of unused data.   This at least has to be fixed ASAP.

Comment 1 Joakim Erdfelt

2012-02-01 20:30:59 EST

Javadoc was added to the distribution back on Sept 16th, 2011
It's been present in the distribution since jetty 7.5.2

Comment 2 Joakim Erdfelt

2012-02-01 20:36:38 EST

Commit'd change to exclude jetty-all from lib directory.

As for the dependency on jetty-all for its javadoc, that would result in generating javadoc 3 times (currently 2 times).  Is this wise?

Comment 3 Greg Wilkins

2012-12-12 16:34:50 EST

The javadoc is no longer in the lib directory, but it is being brought in from jetty-all to the correct location.

One potential fix is to have a jetty-javadoc module that builds the combined javadoc for all of jetty, and then this is consumed by both jetty-distribution and jetty-all.

or we can just leave it as it is for now.

The main thing to avoid is building all the javadoc twice.

Comment 4 Jesse McConnell

2012-12-14 16:39:46 EST

a lot of the current mechanism was to work around issues related to the javadoc plugin in the first place so I'll have a look see to check if that has been fixed up and if so work out a better mechanism for this

it would be grand if we could have a separate module that built and contained an complete javadoc and xref artifacts which could be pulled into the distribution/deployed to downloads.eclipse.org/jetty