commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject Re: [general] (was: Re: [beanutils][lang][PROPOSAL] deprecated beanutils version of MethodUtils)
Date Mon, 28 Oct 2002 00:54:27 GMT

On Sun, 27 Oct 2002, Michael Davey wrote:

> Date: Sun, 27 Oct 2002 20:21:52 +0000
> From: Michael Davey <Michael.Davey@CodeRage.ORG>
> Reply-To: Jakarta Commons Developers List <>
> To: Jakarta Commons Developers List <>
> Subject: [general] (was: Re: [beanutils][lang][PROPOSAL] deprecated
>     beanutils version of MethodUtils)
> Henri Yandell wrote:
> > Ideas for how to handle dependencies better at Jakarta Commons would be
> > good. String Taglib is dependent on Lang and the number one problem users
> > have is not having commons-lang in their classpath.
> More of a workaround than a fix, but I'd like to suggest the following:
>    o  Ensure that there is an 'install' task for each component, that
> copies (or moves) the jar to ${lib.repo}, where ${lib.repo} is
> configured in, say, the users' .antrc
>    o  Use the <get/> or optional <jjar/> task to fetch the dependencies

For use in an application's runtime (where Maven doesn't necessarily help
you set up the class path correctly), one thing we might consider is using
the "Class-Path" attribute of the META-INF/MANIFEST.MF file to explicitly
identify the other Commons JAR files that this one depends on.  For
instance, the following entry in the manifest for commons-beanutils.jar
(once the dependency is added):

    Class-Path: commons-lang.jar

would make things work correctly for users who have a "library"
subdirectory with all of the commons JARs they use in it, (which is a
pretty common occurrence).  This also helps class loaders in some app
servers understand the dependencies better, and reduces the number of
mysterious class not found problems.

> --
> Michael


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message