On Wednesday 11 October 2017 16:04:47 Jean-Baptiste Onofré wrote: > By the way, we provide nightly build of 4.2.0-SNAPSHOT if you want already > try.
I'm already preparing for 4.2 with snapshots, see e.g. SLING-7010 but snapshots are a moving target and no option for early adopters (aka guinea pigs) without access to Apache snapshots repo. Regards, O. > Regards > JB > > On 10/11/2017 03:58 PM, Oliver Lietz wrote: > > On Wednesday 11 October 2017 15:43:34 Jean-Baptiste Onofré wrote: > >> Yeah, but we postponed due to the Java9 issue in dependencies. > >> > >> We are focused on 4.1.3 right now, but 4.2.0.M1 should happen just after. > > > > Having milestones regularly would help to fix issues one by one (or at > > least in small units) when doing major upgrades – the upgrade from 3 to 4 > > was a pain which I really would like to avoid when upgrading to 4.2. So > > having a current milestone without (breaking) changes for Java 9 is much > > appreciated. > > > > Thanks, > > O. > > > >> Regards > >> JB > >> > >> On 10/11/2017 03:41 PM, Oliver Lietz wrote: > >>> On Wednesday 11 October 2017 15:21:52 Jean-Baptiste Onofré wrote: > >>>> Hi OLiver, > >>> > >>> Hi JB, > >>> > >>>> The idea is to cut a Milestone1 release as soon as we have a rough > >>>> Java9 > >>>> support. > >>> > >>> well, 4.2.0.M1 was planned for second week of August... ;) > >>> > >>> Regards, > >>> O. > >>> > >>>> Regards > >>>> JB > >>>> > >>>> On 10/11/2017 03:19 PM, Oliver Lietz wrote: > >>>>> On Wednesday 11 October 2017 15:00:41 Guillaume Nodet wrote: > >>>>>> The point that makes me raise this problem is that the karaf default > >>>>>> distribution uses the Apache versions of xerces and xalan. Fwiw, the > >>>>>> latest xerces release is from 2011 and the latest xalan from 2014, so > >>>>>> they're not the most active. In particular, xalan latest release > >>>>>> does > >>>>>> not > >>>>>> implement jaxp 1.4. > >>>>>> > >>>>>> One additional point is that those libraries stuff is broken on Java > >>>>>> 9, > >>>>>> so > >>>>>> one option would be to remove it alltogether which bring us much > >>>>>> closer > >>>>>> to > >>>>>> Java 9 support ;-) Seriously, I'm not sure I want to spend too much > >>>>>> time > >>>>>> allowing pluggability for specs/implementations while the only real > >>>>>> implementation provider is the JDK itself. That's really a lot of > >>>>>> work > >>>>>> for > >>>>>> no real benefit. > >>>>>> > >>>>>> In addition, the default distribution still install some "legacy" > >>>>>> features > >>>>>> such as aries-blueprint, shell-compat, etc... > >>>>>> > >>>>>> So here's a list of propositions for 4.2: > >>>>>> * remove all libraries for specs / impls from apache-karaf > >>>>>> distro > >>>>>> * remove support for endorsed / ext libraries in the <library> > >>>>>> element > >>>>>> > >>>>>> and wherever used > >>>>>> > >>>>>> * remove aries-blueprint and shell-compat from default distro > >>>>>> * remove a few features from the karaf-minimal distro. I'm not > >>>>>> sure > >>>>>> which > >>>>>> > >>>>>> one exactly, but I think we should get the zip under 10 Mb. Maybe > >>>>>> only > >>>>>> keeping jaas, shell, feature, ssh, bundle, config, deployer and log, > >>>>>> also > >>>>>> removing equinox / logback bundles... > >>>>>> > >>>>>> Thoughts ? > >>>>> > >>>>> +1 > >>>>> > >>>>> And again, I would like to see some milestones before going final/GA > >>>>> to > >>>>> move Apache Sling to 4.2 ASAP. > >>>>> > >>>>> Thanks, > >>>>> O.
