Its beyond that. We said we could not put non-lgpl content into this, so
features like logging need other jars. It also complicates patching. The
best alternative would be to have Class-Path only jar(s) to replace it.
Adrian Brock wrote:
On Thu, 2008-02-07 at 13:18 -0800, Scott M Stark wrote:
> My vote is that jbossall-client.jar is just dropped. Its just duplicate
> bloat that is wrong depending on what features your using.
It's wrong because we don't test against it.
If we fixed the testsuite to only jbossall-client.jar in the classpath
then we'd quickly spot when it wasn't up-to-date.