Ok, keep a lib and lib/ext. However, all that is in these directories
is not necessarily common. Certainly they should not contain all
of the stuff currently there. A large percentage of these so called
common libs would be replaced in a different configuration.

In lib:
crimson.jar - replaceable by any other JAXP compliant parser
jmxri.jar - replaceable by jbossmx, openJMX, tivoli's JMX

In lib/ext:
castor.jar - ???
jbossmq.jar - replaceable by another JMS provider
jbossmqha.jar - replaceable by another JMS provider
log4j.jar - replacable by different versions of log4j
jbossmx.jar - Not even used yet?
mail-plugin.jar - can be dropped or replaced by another javax.mail.Session
factory
hsqldb-plugin.jar - replacable by another DB
...

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Bill Burke" <[EMAIL PROTECTED]>
To: "Scott M Stark" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Friday, February 22, 2002 8:37 AM
Subject: RE: [JBoss-dev] Configuration layout changes...


> Don't move lib or lib/ext under the config directories if you're going to
do
> this.  We don't want multiple copies of jboss core libs hanging around in
> multiple places.  You'll still need a lib directory under
config/default/lib
> for config specific regular jar files.  Or do all jars get placed under
the
> deployer now?
>
> my 2cents
>
> Bill



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to