On 03/07/2012 09:35 AM, Brian Stansberry wrote:
We need to decide what we want to do about usage of the
jboss-common-core library.
A pull request[1] has come in that brings a bunch of jboss-common-core
classes into the AS 7 codebase.
I know in the past we've discouraged use of jboss-common-core for
various reasons, the biggest AIUI being:
1) It's a dumping ground that brings in a lot of unnecessary classes.
2) Some of the stuff in there may not be well suited to AS 7 but is well
suited to earlier, supported releases. So to use it in both basically
means a semi-fork (i.e. branch it.) Forks increase maintenance burdens.
But pulling a bunch of classes out of it and into the AS itself is just
going to turn some module of the AS into a dumping ground. And it's
essentially a fork, but one where the forked code is in completely
separate code bases. I'd rather have people use jboss-common-core than
do that.
[1]
https://github.com/jbossas/jboss-as/pull/1739
Blacklisting org.jboss.util and
org.jboss.net in Tattletale shows:
* jboss-as-cmp-7.1.1.Final-SNAPSHOT.jar
* jboss-as-domain-management-7.1.1.Final-SNAPSHOT.jar
* jboss-as-ee-deployment-7.1.1.Final-SNAPSHOT.jar
* jboss-as-ejb3-7.1.1.Final-SNAPSHOT.jar
* jboss-as-jaxr-7.1.1.Final-SNAPSHOT.jar
* jboss-as-pojo-7.1.1.Final-SNAPSHOT.jar
* (jboss-common-core-2.2.17.GA.jar)
* jboss-jad-api_1.2_spec-1.0.0.Final.jar
* jbossws-common-2.0.2.GA.jar
* jbossws-cxf-server-4.0.2.GA.jar
* jbossws-native-core-4.0.2.GA.jar
* jbossxb-2.0.3.GA.jar
Best regards,
Jesper