[digester][PROPOSAL] optional dependencies

[robert burrell donkin]

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.

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).

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

your comments please :)

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]