Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Disk usage report for Hudson/Build

----- Original Message -----
> From: "Mickael Istria" <mistria@xxxxxxxxxx>
> To: cross-project-issues-dev@xxxxxxxxxxx
> Sent: Thursday, December 13, 2012 11:43:06 AM
> Subject: Re: [cross-project-issues-dev] Disk usage report for Hudson/Build
> Hi,
> For those who are curious to see GMF-Tooling disappeared from the top
> disk users and that would like to see there project consume less disk
> space, here is the GMF-Tooling recipe:
> Facts:
> - maven-javadoc-plugin is the reason why GMF Tooling used to consume
> a
> lot of space
> - Tycho provides easy and efficient ways to make sources available
> - JDT and PDE are smart enough to show JavaDoc when sources are
> available.
> Conclusion:
> - When you ship source features, this enables Javadoc in PDE/JDT
> - So creating and shipping JavaDoc becomes useless in IDE while you
> provide sources.
> Actions:
> - We removed maven-javadoc-plugin and rely only on source bundles. It
> does not affect users in their IDE, who still see JavaDoc from
> sources.
> Results:
> - Build is cleaner (one less complex maven-plugin)
> - CI uses less disk space.

What about if one needs to provide real browsable javadoc as platform does it? If a project provides or at least try to provide an API that others can use to extend it relying on source bundles is not sufficient as people need to look at the API to get an idea how things are supposed to work and what the framework is capable of doing prior to starting to write code. 
If the project doesn't try to provide any framework relying on source bundles is enough I agree.

Alexander Kurtakov
Red Hat Eclipse team

> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx

Back to the top