I for one don't see how bloat comes into it. Nothing stops the Axiom project from having a build that produces multiple jar files that are loosely coupled. The discussion here is about the conceptual overhead of formal component process.
On Wed, Feb 18, 2009 at 2:40 AM, David Illsley <davidills...@gmail.com> wrote: > Thanks for the information. I'm generally unconvinced by the argument > that having an optional 100KB axiom-xmlsecurity module counts as > 'bloat'. To me it's better for users for it to be part of Axiom > because information about this additional functionality that Axiom > users may wish to use will be more obvious. From an Apache > perspective, I think having it part of Axiom would have a couple of > advantages... > 1. Fewer dependency projects which need to be lined up for new > releases of e.f. Axis2/Rampart2 > 2. Giving it a separate name encourages people to think of it as > something separate and owned by a separate community which, given the > size of the codebase seems unnecessary. I think it does properly > belong as part of the Axiom community > > David > > P.S. What does 'thomara' mean and have you done the appropriate name checks? >
