Re: [PROPOSAL] version 2.0?

[Geir Magnusson Jr .]

On Wednesday, November 27, 2002, at 01:26 PM, Bill Burton wrote:

  - Ant Logger (currently in DVSL)

why?

Because it makes integrating Velocity with Ant easier. Anakia should probably use this logger, vDoclet has it's own solution, xDoclet is being rewritten to use Velocity and will need integrated logging, etc., etc.

I haven't looked at what vDoclet does for logging integration but if it's a better solution, maybe it could be used instead.

Ah - right. This is why I'm resistant to putting things like this in the velocity core, as when you find something different/better, we have to support the old.

Instead, if they were in Velocity tools, with good docs, then it's a natural thing to have *that* be the place for extensions like this. Still supported, still documented, still good code - but not part of the core.

  - #local directive

no... :)

Okay.

:)

Sorry - I didn't mean to be that abrupt. See above re the tools - are there really enough people using #local that it warrants inclusion in the core? I threw that together in about 10 minutes, if I remember. That people are using it is thrilling (and scary... :) but I think that tools would be a great place.

* Other architectural changes
  - Way of passing state to a Resource Loader

?

Of course, anything like this is open for discussion. I just threw it out as it's something myself and others seem to have needed.

What is it?

I don't think a 2.0 is warranted unless the float change is significant enough. I guess if it is, then indeed a 2.0 is right.

I don't think it has anything to do with how significant the internal changes are but more that it has the perception of major new functionality. It's *much* easier to tell people they need 2.0 for these these features than to say that 1.4 is needed for one feature and then 1.5 adds some other new feature, etc. Also, with a major revision change, people will *expect* major new features.

Right - but I think that we aren't adding new things here. I see 2.0 as a big step.

Also, releasing 2.0 may mean the possibility of allowing slight issues with backwards compatibility (such as with floats and division). But of course, every effort should be made to maintain backwards compatibility with the 1.x versions.

It's clear 1.3 is overdue. I'll release it ASAP and get the patches in.

Well, when you have the time.  We all know you're busy these days.

I'm going to make the time. This whole thread has upset me quite a bit (hence my snapping at Christoph - I'm sorry...) and caused me to look around a bit at things. Changes need to be made.

<sigh>

--
Geir Magnusson Jr 203-355-2219(w)
Adeptra, Inc. 203-247-1713(m)
[EMAIL PROTECTED]


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>