Craig McClanahan wrote:
I can certainly buy into release consolidation along these four paths. That being said, separating the source artifacts (and the binary jar files that result from them) is still useful in terms of clearly articulating dependencies *within* a particular release. That becomes much more important as we offer finer grained jar files that are optional but impose their own external dependencies.
Certainly correct me if I'm wrong, but wouldn't this proposal more or less do away with the idea of offering finer grained jar files? Except for Tiles, which I know is being spun off on its own (I presume so the same code base can support Struts, Shale and anything else?), are any of the other "dwarfs" in the same kind of boat as Tiles? It sounds from this proposal like they may not be?...
Don Craig
Frank -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
