Currently we are including 1.5.x version of Oak in Sling which are considered unstable. Not sure on best way to deal with that.
One way out could be to align release of launchpad in Sling with major version release of Oak which typically happens once in year around Feb-March. This would allow us to include the latest stable release of Oak in launchpad and would also ensure that any feature work in Sling which rely on Oak also get completed. For example currently the Sling Listener feature needs some further work and has some dependency on works being done around observation event filtering in Oak Thoughts? Chetan Mehrotra On Fri, Sep 30, 2016 at 6:52 PM, Daniel Klco <dk...@apache.org> wrote: > Okay, that should be very doable. I'm 80-90% sure all of the code changes > are there. I'm just running into a wall trying to test it out, I opened > another email thread to discuss that issue. > > On Fri, Sep 30, 2016 at 9:18 AM, Carsten Ziegeler <cziege...@apache.org> > wrote: > >> Daniel Klco wrote >> > I'd also like to include the changes I've been meaning to make for >> > normalizing the scripting cache clear. Affected modules are: >> > >> > - org.apache.sling.commons.classloader >> > - org.apache.sling.commons.fsclassloader >> > - org.apache.sling.scripting.jsp >> > >> > What's the target release date for Launchpad 9? >> > >> We don't have a target date, but it should definitely happen this year :) >> It would be great if we can make end of October though I think >> >> Carsten >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> cziege...@apache.org >> >>
