I would frame it this way:
1. We have a shared utility subproject that would host an assortment of
components.
2. We have a subproject for each component.
3. Each subproject may host a utility library, which other subprojects
can use.
(1) or (2) are going to depend on whether anyone has an itch and takes
the initiative. Otherwise, we default to (3). This might not actually
be a bad thing, so long as we have some type of CJAN facility so people
can find what they need.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
