Peter Donald wrote:
> Changing a projects charter from server-side component repository to
> component model so that another project can become a server-side component
> repository is not something that I think I would like to do ;)
One of the ideas that seems to be getting lost is the model of a
component repository that is different from Avalon. Where Avalon is a
single project entity that has multiple components, the other model is a
place that holds/hosts multiple projects, each of a single component (or
so). Basically the jakarta 'group of individual projects' model on a
smaller length scale.
I assume that Sam is going to ask again (correctly) about why this
matters - if in the end the result is a set of components, why is the
difference important.
What I think makes it different is related to focus and packaging.
n the new model (!Avalon), I believe the separation of projects would
force each component to be adequately packaged and documented, since
each is a separate entity with possibly different committers, different
users, and a different charter. In contrast, I believe the Avalon model
gloms all the components into a single jar and they aren't individually
documented. (This is also the case for frameworks like Struts and
Turbine.)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
