What is our policy on inter-project dependencies? I just had to copy a method from commons-lang, because I didn't want to introduce a runtime dependency (http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200509.mbox/%3 [EMAIL PROTECTED]). That seems, as Henning pointed out, silly to me. And, the commons-email release was shot down because of its dependence upon commons-lang. The dependence in email, though, was exposed in the public API. In proxy, the dependence is upon the ClassUtils.getAllInterfaces() method inside a couple of class' implementations. Is this okay? Or, should I strive (as I already have done) to keep the dependencies to a minimum? I do have a runtime dependency upon Commons Logging at this time also.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
