Quoting [EMAIL PROTECTED]: > What would you like to see consolidated? > > I'd prefer Jelly didn't go the way of Ant and integrate a whole swag of > stuff into the 'core', so that the core could be free to be changed easily > and extended.
Agreed, though what should be in the core? A minimum but useful set. For example, the core, xml and define tag libraries, but what about util? At the moment, a clean build of Jelly and Maven results in a huge number of jar downloads, and it'd be nice to know what's *really* requires by the Jelly core, and what's required by the various tag libraries. Building a particular tag library would then get it's own dependencies. James, are the changes to the build process you were talking about going to move things this way? If so, I would say this should be in place before a move to top-level project or commons proper. James -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
