commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject Re: [digester][PROPOSAL] optional dependencies
Date Mon, 29 Sep 2003 17:09:48 GMT
robert burrell donkin wrote:

> i think that it's important that digester retains the smallest 
> possible set of core dependencies. but i'd like to be able to supply 
> users (who need this functionality) with more exotic toys such as 
> regular expression based pattern matchers based on ORO or regexp. i 
> think that the best way to go forward would be adopt the strategy that 
> ant uses and separate out core dependencies from optional ones. the 
> basic, default configuration should run with only the core dependencies.


The core is currently dependent on beanutils, collections, and logging.  
That's a list I would prefer not to extend.

> i'd like to concentrate these optional dependencies under the 
> org.apache.commons.digester.optional package. i'd also like to 
> structure the build so that no class in core can depend on any in 
> optional. i'd also like to put these classes into a src/optional-java 
> directory (rather than src/java).

+1, parallel to the new examples directory.

> i'm not sure whether it would be best to distribute a single digester 
> jar or whether we should ship two jars.

Ant ended up with two jars in the same situation, and I think that's 
probably a reasonable approach.

> your comments please :)
> - robert


View raw message