Re: [JBoss-dev] Rebuildable jbossall-client.jar
The jboss-allclient.jar in its current form is just a broken concept to
simplify client classpaths. Without an expression of installer artifacts
like client jars, its not maintainable. This is the direction Alex
Pinkin is working on. Ultimately a jbossas build defines its component
dependencies and each component has an installer descriptor that defines
the types of installer elements relative to the standard binary
distribution structure (client jars, server jars, deployments, docs,
examples, ...) and this is used to build either the zip distribution or
installer. This replaces the current build-distr.xml script that is not
being kept up to date.
Jason T. Greene wrote:
We have historically had pluggable web service stacks in JBoss AS,
typically for the purpose of backwards compatibility. More recently, we
have also been providing updates that are pluggable on a particular
version of AS. For example, right now you can update a 4.0.4 instance to
use jbossws 1.0.2. I am sure that as time goes on other projects will be
doing similar things.
The problem with providing pluggable components in AS is that if any
part of that component is contained in jbossall-client.jar, it is likely
to contain conflicting or stale classes.
I can envision two solutions:
1. It is the responsibility of the component provider to have some kind
of install process that updates the jbossall-client.jar.
2. We provide a jboss/bin/rebuild-allclient.sh that reconstructs the
jar.
Any thoughts on this?
Thanks,
-Jason
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Jason T. Greene
Senior Software Engineer
JBoss division, RedHat Inc.
Xxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development