> On Thu, Apr 22, 2010 at 6:27 PM, Bertrand Delacretaz > <[email protected]> wrote: >> Hi Vidar, >> >> On Thu, Apr 15, 2010 at 11:32 AM, Vidar Ramdal <[email protected]> wrote: >>> ...does anyone know a full set of recently released Sling bundles >>> that are known to work together?... >> >> I'll try to break this loud silence ;-) >> >> I think starting with the launchpad from trunk, and going back to the >> last released version of each bundle is the way to go. If that leads >> to missing dependencies, as your tests seem to indicate, I'd suggest >> releasing the minimal set of bundles that fixes this problem, and then >> make a launchpad release. Once that's done, repeat at very regular >> intervals (every 2 months?) to avoid the problem in the future. >> >> I have no idea how much work "releasing the minimal set of bundles" >> represents now, maybe you could post more details about your tests so >> that we can collectively look at what's needed?
On Thu, Apr 22, 2010 at 9:30 PM, Vidar Ramdal <[email protected]> wrote: > [...] There's an inconcistency with these two: > - o.a.s.sling.scripting.core 2.0.10 > - o.a.s.jcr.resource 2.0.6 Since SLING-1304 [1], the currentNode binding is no longer set in scripting.core, but instead in jcr.resource. This means that running these two bundles in those versions leaves me with no currentNode binding. PS: Justin - SLING-1304 does not have the 'version' field set - we should probably set it, so that the issue will be listed in the generated release notes. It seems the change affects scripting.core 2.0.10 and jcr.resource 2.0.8 - can you confirm? [1] https://issues.apache.org/jira/browse/SLING-1304 -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
