<snip>
I figured the munging would be unlikely to pass muster. The easy solution is that BeanUtils/Net are not allowed into a combo-distribution until their dependencies are. So ORO/commons-logging would have to be in it. One problem there is commons-logging's dependency on log4j, logkit and avalon-framework.
i've been thinking for a while that several components will soon be reaching the stage commons logging reached a while ago. digester and beanutils (for example) are going to want to add non-core dependencies for optional plugins sometime soonish.
commons-logging does not require log4j, logkit or avalon-framework to function in it's basic configuration. the case (when the time comes) will be similar for digester and beanutils. additional dependencies will be required if the user wants to plugin some optional functional but not to for the core component.
i think that there a strong case to be made that it's only core dependencies that should concern the assemblers of the combo bundle. it is therefore not unreasonable to include commons-logging (and any commons components that depend on it) within a combo release.
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
