Here's a proposal  to add source bundles to the jbosstools target
Currently, to get a TP with sources you have to build it locally with
mvn install -Dmirror-target-to-repo.includeSources=true .
With this change, you can simply download the zipped target platform
site and have all the sources you need for debugging and development
already in that archive.
If you DO NOT like the above idea, please -1 this issue, or it'll be
applied in the next 36 hours (prior to target platform code freeze on
Note too that once this is applied, Fred's PDE Source Lookup tool 
can be used to automatically discover sources even if you haven't
downloaded the whole target platform zip.
Artifact sizes before/after this change:
4.60.x TP zip: 491M -> 766M
4.60.x TP site: 528M -> 824M
1) When building the TP locally, you were previously already
downloading the same sized content, but one file at a time rather than
as one large zip... so you're actually saving 824M-766M = 58M of
download (but now have to unpack it locally to use).
2) The amount of disk needed to build the TP with sources locally is
1.6G. Downloading the zip and unpacking it will use the same
footprint, but then you can immediately recover the 766M used by the
3) You can still resolve a target platform locally and disable
fetching of sources with -Dmirror-target-to-repo.includeSources=false,
if you want the smaller 528M footprint on disk or don't need sources.
4) For those in Europe, we could set up mirroring between
(in Boston) and a server in Brno, so you can get
the TP zip from a European server & save time.
5) The devstudio TP site and zip are not affected by this proposed change.
6) PDE Source Lookup tool can start discovering sources, even if you
DON'T download the whole TP first (this should also work with a Brno
mirror if you manually add it to Eclipse's Available Software Sites).
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio