Hi Nicolas, On Mon, Mar 29, 2010 at 10:15 AM, Nicolas Delsaux <[email protected]> wrote: > We're currently trying to evaluate sling and, for that, we downloaded > sources according to > http://sling.apache.org/site/getting-and-building-sling.html and found > various compile issues....
> ...Are these issues in > experimental projects ? And if so, is it appropriated to let users use > svn trunk branch as playground ?... The trunk is supposed to be stable at all times, but we're not religious about it so it can be broken from time to time (and whoever broke it should fix it, hint, hint ;-) The best way to find out about the latest SVN revision that passed all of our tests (which have a reasonably good coverage, at least for the core things) is to look at our Hudson continuous integration builds. Looking at http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/ now, for example, shows that the latest build had a number of failed tests, but build #348 was all green. You can then find which SVN revision was used for that build, and use that for your evaluation. Looking at http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/changes (not sure if there's a better way) will tell you the number of the last SVN revision created before a given build. For build #348 that's revision 927092, so if you svn export that revision you should get a clean build with JDK 1.6 (using Maven at the command-line like Hudson does). The most important/most tested modules are those in the "bundles" folder, the other folders contain extensions/samples/optional components that might not be always stable. Hope this helps - we really should to a launchpad release soon, for people like you who want to play with a stable release. -Bertrand
