Hi. On Mon, Jul 7, 2014 at 12:25 PM, Bertrand Delacretaz <[email protected]> wrote: > Hi, > > Unless I'm mistaken, I see only binaries at > https://dist.apache.org/repos/dist/release/sling/eclipse/1.0.0/ - did > we release the source code as well, and where?
Hm, you're right. The 'release' artifact was the p2 update site at [1], but that only contains binary artifacts as well. The source jars are only in Nexus for now. I can see several ways out: 1. upload all jars + source jars ; this has the slight disadvantage of polluting the repo with 15+ new jars. One way to alleviate that is to place them under sling/eclipse ( but then we probably need to restructure sling/eclipse a bit ) . It's also worth mentioning that due to the way Eclipse plug-ins are built, one single source can not be built standalone, or at least not trivially. The way to build them is to use the reactor build. 2. Upload a source bundle of the whole project, which can then be used to rebuild the project using mvn package. > Also, I think the http://apache.org/dist/sling/eclipse/1.0.0/ HTML > page should include a disclaimer that what's there are only > convenience binaries, and that people should build them from source if > they want the official Apache release. Maybe point to a new page on > our website that explains this better and that can be reused for > similar such releases? Agree, I'll update the template. As for the documentation, I would add an 'Installation' section to [2] and reference it from the update site. Robert > > -Bertrand [1]: https://dist.apache.org/repos/dist/release/sling/org.apache.sling.ide.p2update-1.0.0.zip [2]: https://sling.apache.org/documentation/development/ide-tooling.html
