On 5/3/02 9:51 AM, "Waldhoff, Rodney" <[EMAIL PROTECTED]> wrote:
> You mean this? > >> [jakarta-commons] shall create and maintain packages written >> in the Java language, intended for use in server-related >> development, and designed to be used independently of any > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> larger product or framework. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > That seems like a pretty straightforward requirement. It doesn't really > speak to the dependencies, but rather to use: I could have, for example, a > commons component that depends upon Struts or Turbine, it seems to me, as > long as the are usable outside of Struts or Turbine. Otherwise it's pretty > silly to put it in commons. > > For a concrete example, in theory one could create an implementation of > commons-pool that uses the avalon-excalibur pool implementation. The > commons-pool interface, and generic implementations of it, remains usable > outside of avalon/excalibur. Only if I want to use that particular pool > implementation do I need to bundle avalaon-exaclibur with my client code. > That makes perfect sense. -- Geir Magnusson Jr. Research & Development, Adeptra Inc. [EMAIL PROTECTED] +1-203-247-1713 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
