Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
From: Oliver Lietz <apache@oliverlietz.de>
To: dev@karaf.apache.org
Subject: Re: [DISCUSS] Trim down karaf distributions for 4.2
Date: Wed, 11 Oct 2017 15:19:40 +0200
Message-ID: <3696417.NZ7fW6OqoR@madness>
User-Agent: KMail/4.14.10 (FreeBSD/10.2-RELEASE; KDE/4.14.10; amd64; ; )
In-Reply-To: <CAA66TpoE3t_8WHCvDRkOS=xR8xBdkK+QVFwnvntuC1f6tPLv5w@mail.gmail.com>
References: <CAA66TpoE3t_8WHCvDRkOS=xR8xBdkK+QVFwnvntuC1f6tPLv5w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
archived-at: Wed, 11 Oct 2017 13:19:57 -0000

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.