commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Libbrecht <>
Subject Re: [Jelly] Dependencies Question
Date Mon, 14 Feb 2005 20:57:01 GMT
As with most dependency... each jar is only for a given purpose... if 
you don't use that purpose you don't need it!
I think maven is considering assigning roles to dependencies since long 
but... how do you express that dependency X is only for functionality Y 
in general?

 From your list,  I think you can remove log4j, commons-collections, and 
commons-cli if you use the embedded jelly (do check, not sure for 
commons-collection). Beware that you seem to include neither xml-apis 
nor an xml-parser so that you are ok to rely on Crimson (some don't 
like it) and to require jdk 1.4....

You must be doing something very small if not using jelly's xml or ant 


Le 14 févr. 05, à 21:43, Dion Gillard a écrit :

> On Mon, 14 Feb 2005 15:21:06 -0500, Peter Walsh <> 
> wrote:
>> I'm reviewing the jelly project to see if it is appropriate for my 
>> uses.
>> The sample project I've created includes much fewer jars than what is 
>> posted
>> at  
>> Specifically,
>> I'm only inlcuding the following:
>> commons-cli
>> commons-collections
>> commons-beanutils
>> commons-jelly
>> commons-jelly-tags-define
>> commons-jexl
>> log4j
>> dom4j
>> Will I run into any problems not including all the jars that are 
>> listed as
>> dependencies in my classpath?
> Some dependecies are for the command line interface only, e.g.
> forehead or commons-cli. If you are using the Embedded class to run
> Jelly scripts you may not need these dependencies.

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

View raw message