Community
Participate
Working Groups
Build ID: 0.8.0 (Indigo) I can't find any prebuilt source bundles for linuxtools. This is a problem for us, since our company has decided to ship source for any EPL code that we include in our product, in order to comply with the EPL requirement of making the exact version of source available that's used in a build. I'd prefer downloading prebuilt source rather than packaging these myself. I've heard that creating source bundles is easy with Tycho but haven't done it myself yet. Perhaps the parent POM from bug 339915 can help. It would be super helpful for us to get source bundles built in 0.8.1.
The problem is that tycho supports generating source bundles but doesn't support generating source features. So source features have to be made manually in order to get the source bundles generated. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=345234 for details. And manually creating a source feature for every feature in Linux Tools is too time consuming
*** Bug 300203 has been marked as a duplicate of this bug. ***
We ship source bundles now.
http://download.eclipse.org/technology/linuxtools/0.9.0-sources/
I think Martin was requesting .source OSGi bundles but I'll let him re-open if I'm correct.
Sorry, my bad. And I'm even the one that explained the showstopper.
In fact I had originally thought about OSGi source bundles, but the tar.bz2 archives made available are actually good enough for our purpose as well. We need the sources in order to pack them on our product DVD such that we comply with the EPL requirement to "make source available". We don't really care what our customers do with the source so we don't care much about format... except we need to be able to easily modify the provided source package in case we have to modify the source for fixing a defect. The benefit of OSGi source bundles is that they allow debugging the deployed product easily (provided you have PDE). That's another use case mostly interesting for deploying into Open Source, but not a must-have for us since we don't even ship PDE or JDT with our product. Long story short, OSGi source bundles would be nice for us since that's what all the rest of Eclipse does so we wouldn't need to adjust any of our releng, but the tar.bz2 is good enough for our original requirement. BTW, on a quick browse through the source archive, I was surprised that the helgrind.tests plugin includes template_cachegrind.txt files ?
I've opened bug 364198 to address the *cachegrind* files in the helgrind test plugin. Thanks for the clarification on the source requirement. I'd still like to see us comply with the standard way of doing things. I believe there is some work going on in Tycho to support OSGi source bundles.
Ping, any update on this ? As valgrind is going towards 1.0 I'd think it's important to have source bundles built... since some adopters may have a legal requirement to ship source with their offering. In my understanding, the current "state of the art" with respect to source bundles is that Tycho generates them automatically, but a feature needs to be hand-written to pull them together into the repo. I haven't written such a feature myself so far, but I know that CDT has. See also bug 304376 .
I'm planning on looking at this for 1.0 (so, in the coming months). Thanks for the pointer to the Tycho details.
A quick knowledge dump: 1. Tycho can make source bundles easily http://wiki.eclipse.org/Tycho/Reference_Card#Source_Bundles 2. Tycho now appears to have the ability to automatically generate source features to contain said .source bundles https://bugs.eclipse.org/bugs/show_bug.cgi?id=345234 http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/commit/?id=8831506f29b3ebf78d294f80df287ba8eb536c56 We could make a -sdk feature that lists all the .source bundles but I worry it will get out of sync with reality; hence my interest in the automatically-generated SDK-type feature for the .source bundles. I will continue looking into this.
Implemented in master now. Source features are generated for every feature we have in the update site and source bundles for every bundle in the feature (without help/docs aka missing source.. in the build.properties) are generated and available on the update site too.
I can confirm these work for me with PDE. Thanks, Alex! The source bundles all have blank feature names which looks weird in the p2 UI (on the "Install Details" page). Is there a way to fix this?
Probably there is but just putting featureName= in the feature properties didn't worked so I don't know an easy way.
I filed bug 372657 to track adding feature names for the source bundles.
