+1 (non binding) regards Grzegorz Grzybek
2017-10-11 15:05 GMT+02:00 Andrea Cosentino <[email protected]>: > +1, it makes sense. > Cheers, > -- > Andrea Cosentino > ---------------------------------- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix PMC Member > Email: [email protected] > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Wednesday, October 11, 2017, 3:01:07 PM GMT+2, Guillaume Nodet < > [email protected]> 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 ? > > -- > ------------------------ > Guillaume Nodet > >
