You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Will Glass-Husain <wg...@forio.com> on 2005/10/11 00:20:35 UTC

Re: whitespace

Hi,

If you're genuinuely interested in where to find past discussion on this
issue... two good resources are the project roadmap on the Wiki and the JIRA
issue tracker.  The home page of JIRA allows you to see what issues have
been completed and are scheduled for different releases.  (You'll find the
whitespace issue under 2.0).  There's also a page dedicated to discussion of
this issue in the Wiki, and about 50 messages on the velocity-dev mailing
list debating pros and cons of different approaches.  (it's not scheduled
for version 1.5 as it does not fit the goals of 100% drop-in replacement to
earlier versions).

Best,
WILL


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org


Re: whitespace

Posted by Jonathan Revusky <re...@wanadoo.es>.
Will Glass-Husain wrote:
> Hi,
> 
> If you're genuinuely interested in where to find past discussion on this
> issue... two good resources are the project roadmap on the Wiki and the 
> JIRA

Well, on the specific question I posed, the person I was addressing, 
Christoph Reck, should also be a good resource. He said that this 
whitespace debate had taken place and it had been resolved that it would 
work the way it is described on that wiki page he pointed me too.

So, it seems like a natural question to ask when the debate occurred and 
what progress has been made on this since then... Presumably, Christoph 
was involved in that discussion, and thus knows when it took place. 
Also, since it does seem to be a big issue for Christoph, he would also 
likely be aware of what progress (if any) that had been made on 
implementing this.

So it seemed reasonable to me to ask him about this. If Christoph (or 
you or anybody else, for that matter) can just tell me the answer 
straight away, it strikes me as a more efficient way to get the 
information than, say, rooting around on 5 years worth of mailing list 
archives. Even if I were going to do this, just to tell me approximately 
when the discussion occurred would be helpful.

> issue tracker.  The home page of JIRA allows you to see what issues have
> been completed and are scheduled for different releases.  (You'll find the
> whitespace issue under 2.0).  

2.0? I don't recall ever hearing about a Velocity 2.0? Is there actually 
a branch that I can check out that has some beta or alpha-level 
whitespace gobbling implementation? I actually would have some 
professional interest in looking at this, since I am not 100% satisfied 
with my own implementation of the same thing in the FreeMarker code.

Now, while I am somewhat interested in finding the answer to the 
questions I posed, other people who actually use Velocity and want this 
whitespace gobbling are probably far more interested than I am. I guess, 
if you and Christoph, for whatever reasons, won't answer my questions, I 
could go look at the resources you mentioned and report back my findings 
for general edification. If you guys won't answer the question, I cannot 
really see what legitimate objections you could have to this. Moreover, 
it is clearly and unequivocally _on-topic_.

OTOH, maybe you should just behave in a forthright, responsible manner 
and answer these things: When did the debate over the whitespace occur? 
In the interim, what concrete progress has been made on this?

(Between you and me, I think that refusing to answer the question makes 
you look even worse than answering it does... It starts to look like 
some ludicrous variant on "taking the fifth". "I decline to answer this 
question on the grounds that the answer might tend to make us look like 
lamers..." :-)

Regards,

Jonathan Revusky
-- 
lead developer, FreeMarker project, http://freemarker.org/

> There's also a page dedicated to 
> discussion of
> this issue in the Wiki, and about 50 messages on the velocity-dev mailing
> list debating pros and cons of different approaches.  (it's not scheduled
> for version 1.5 as it does not fit the goals of 100% drop-in replacement to
> earlier versions).
> 
> Best,
> WILL


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org