Tim Colson said: > Broken collarbone as of Sunday, so I'll be quick/short... typing is mosly > 1-handed at the moment.
sorry to hear that. :( > 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 ... yeah, but the website isn't much of an authority figure as far as i'm concerned. that category could just as easily have been called "Related Projects." where would your argument be then? > 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. if you want to get them out of the core, why aren't you arguing for them to be put into the dvsl sub-project? certainly they have more in common there... > 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, oh yeah, that's right, because DVSL doesn't have the word "tool" in it's name. sheesh. all this just makes me want to change the name of the VelocityTools project. what if we called it "firebird"? ;) > 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. AFAIK, the website (which doesn't get to vote in this matter) had a "Tools" category with things like Anakia/Texen/Veltag/etc in it before there ever was a VelocityTools/Struts project. They were listed as "tools" on their own before their ever was a new "tools" subproject to integrate velocity with struts. in other words, the "tools" category on the main website is has never been parallel or equated to the unfortunately named VelocityTools subproject. So it is a non sequitur to conclude from this "indisputable fact" that Anakia/Texen should be in the VelocityTools project. And also note that if such a conclusion were reasonable, it would also then be reasonable to put every other bullet item in that "Tools" category on the website into the VelocityTools project. and i hope you at least agree that that would be a bad 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. i really don't see the problem with putting them in their own subproject. that's better than just having them "clutter up" another project instead. i don't care how few or many files are in a project. but it's not really my call. > Ah well, I'm going to be forced to use JSTL instead of Velocity soon anyhow. > ;-) bummer. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
