On Wed, 2016-12-21 at 17:07 +0100, Oliver Lietz wrote: > On Wednesday 21 December 2016 16:16:36 Bertrand Delacretaz wrote: > > On Wed, Dec 21, 2016 at 4:02 PM, Robert Munteanu <romb...@apache.or > > g> wrote: > > > ...What would be the disadvantage of working with SNAPSHOTs in > > > branches > > > and merging back to trunk once we have releases of the respective > > > projects?... > > > > IMO the problem is that this makes that work essentially > > "invisible" > > to others as we do not usually work with svn branches. > > Good point. > > > We could use instead a Maven profile in the main pom for such > > modules > > that require external snapshots. Disabled by default, so the trunk > > builds and one can easily re-enable those modules as needed. > > That does not work unfortunately. The Sling Karaf modules will fail > with > latest Sling releases because of missing R6 Http support. > I stopped updating some dependencies (using the Http Whiteboard, e.g. > Engine, > Rewriter, i18n) but the gap is getting bigger and bigger every day > and hard to > catch up. Other parts of Sling are also moving fast and need special > attention > (e.g. Login Admin Whitelist and system users). > > I'm close again (test with Oak Mongo is broken and > org.apache.sling.karaf- > launchpad-oak-tar-integration-tests has issues) at the cost of not > having a > Jenkins build until all required upstream projects are released.
I double-checked, and the Karaf modules are not part of the main reactor anyway. How far away are we from upstream releases of Karaf and Pax-Exam? Robert
