To be honest, I've always thought the primary reason the "Tools" and "Velocity Core" are separate had to do with access control, release schedule, and quality control.
Geir and the few other Velocity committers have kept tight control over the source control for Velocity, with an articulated goal of keeping the core language simple and backwards compatible. (there's downsides to this, of course, such as a multi-year release cycle). Breaking out the tools project allowed Nathan and others to have flexibility over creating updates and issuing releases. So, I suggest three criteria to decide whether or not Anakia/Texen should be part of the "core". --> Are there people interested in maintaining & upgrading the code (outside of the core committers)? This is critical. --> Does it live outside of the strict quality control umbrella of Velocity core (e.g. keep the language clean and backwards compatible at all costs) --> Does it require a release schedule different than Velocity? It's not clear to me that "logical organization" matters so much, as opposed to the above bullets. WILL ----- Original Message ----- From: "Tim Colson" <[EMAIL PROTECTED]> To: "'Velocity Developers List'" <[EMAIL PROTECTED]> Sent: Tuesday, June 29, 2004 8:09 AM Subject: RE: Velocity Core and Tools separation > Broken collarbone as of Sunday, so I'll be quick/short... typing is mosly > 1-handed at the moment. > > Nathan said these things: > > i agree that Anakia/Texen probably ought to be > > moved out of the core, but i just don't want them in VelocityTools. :) > > > c'mon. i'm not saying it's not a tool in the general sense of > > the term. if you can explain to me how Anakia is similar in > > function/use/purpose to the contents of the VelocityTools project, i'll > listen. > > > i still haven't heard you justify their inclusion with > > something better than the vague semantics of the word "tool." > ------ > I'm just saying that the website already lumps those "other things" into a > Tools category, but in the distro they are in CORE-- not Tools, not > VelocityTools, not "Other things Nathan doesn't want in Tools because it's > not a "Velocity Tool"... well, or it's not a Servlet which is okay... > certainly not a "tool" like "Struts Message Tool" is a "tool", but it can > use a toolbox, so it's okay... especially cuz' Nathan likes servlets.". > <grin> > > I don't see how a half dozen Anakia classes will ever live on their own as > jakarta-velocity-anakia. And in 3 years, I haven't seen those other things > change much at all. I'd be willing to help move/maintain (fwiw) those other > things as sub-areas of the jakarta-velocity-tools project out of the desire > just to get them out of core, and make things seem a bit more logical. > > The broad semantics of the word "tool" is exactly the reason why I can > easily see these things which are not CORE going into Velocity Tools, that > and the indisputable fact that somebody at some time filed them into a > "Tools" category on the website, so I'm not the first idiot to come up with > the idea. > > But I'm not interested in this little argument... so that stuff will > probably live on cluttering up the core, because no better alternative has > been given to putting them into jakarta-velocity-tools. > > Ah well, I'm going to be forced to use JSTL instead of Velocity soon anyhow. > ;-) > > Cheers, > Tim > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
