My understanding of the lib vs lib/ext split was based on which jars had to be
in the system classpath vs the JBoss server MLet based class loader. For example,
jaas.jar and jboss-jaas.jar must be on the system classpath due to limitations
with the JAAS class loading approach. All of the jars in the lib directory are in
the bin/run.jar manifest Class-Path.
----- Original Message -----
From: "Chris Kimpton" <[EMAIL PROTECTED]>
To: "JBoss-Dev" <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 3:08 PM
Subject: [jBoss-Dev] [PROPOSAL] merging lib and lib/ext
> Hi,
>
> I am trying to make the build file simpler ;-)
>
> [so that switching xml parsers is easier...]
>
> I've switched to a newer version of ant and changed build.xml to use some of
> the new features.
>
> This leaves one place in the file that explicitly refers to the xml parser -
> the bit that decides what goes into lib versus lib/ext.
>
> I can't see that this split is needed - can anyone give me a reason for it?
>
> I want to remove it - instead putting all jars into the lib directory - thus
> removing the above need to define the files that go into the one directory
> over the other.
>
> Thanks in advance for your comments,
> Chris
>
>
>
