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
cdf9h71$c9j$2@tangens.hometree.net%3e). 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
|