from:"Geir Magnusson Jr."

Re: ApacheCon NA 2017

2017-01-04 Thread Geir Magnusson Jr.


> On Jan 4, 2017, at 10:57 AM, Christopher Schultz 
>  wrote:
> 



> But I'm
> perfectly happy to stand up in front of people and talk about technology.

+1!

Do it!

> 
> Is anyone else planning to attend? Would anyone be willing to present?
> 
> Thanks,
> -chris
> 


-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Re: Velocity Macro Stack Traces Patch

2012-10-10 Thread Geir Magnusson Jr.


On Oct 10, 2012, at 9:22 PM, Benson Margulies bimargul...@gmail.com wrote:

 
 Meanwhile, neither of you have made a contribution through this
 discussion :(
 
 It is important that Apache projects and their contributors understand
 Apache policies for contributions. I'm sorry if you don't agree, but I
 hope that the PMC members of this project see the value.

I agree.  I don't ever think that there is harm in people understanding how 
things work.

geir


-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Re: [VOTE] Release Velocity Engine 1.6

2008-12-01 Thread Geir Magnusson Jr.


+1

On Nov 28, 2008, at 10:08 AM, Nathan Bubna wrote:


Ok, there were no complaints about the current test build that were
worth generating a new test build and delaying this (IMO), so i'm
moving on to a vote.

The test build candidate for release is still available here:
http://people.apache.org/~nbubna/velocity/engine/1.6/

Please vote regarding your support for releasing this new test build  
as

Velocity Engine 1.6:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close time as
roughly 7am PST on Monday, Dec 1st.  If the vote passes, I'll push
this to the mirrors and change the web site and get Henning to  
deploy it.

With luck i'll be able to announce it by Wed.

On Fri, Nov 21, 2008 at 11:38 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:

ok folks, i think the time has come; here's a build for Engine 1.6:

http://people.apache.org/~nbubna/velocity/engine/1.6/

please kick the tires and report any and all nitpicks soon.  PLEASE
try it out and look for problems.  (yes, i am begging!)  assuming no
one sees any problems, i'll call for a release vote next friday.

thanks,
nathan

p.s.  this release should rock; here's a rough list of new things in
this release:

Major memory and speed performance improvements
varargs support for object method calls
#evaluate( $stringthatcontainsvtl )
#define( $body ) for VTL blocks as references #end
#break for ending #foreach loops prematurely
Static utility methods via context.put(Math, Math.class)
fixes for many annoying little syntax/parsing bugs
#parse( mymacros.vm )
CommonsLogLogChute, ServletLogChute
Fixed and much improved StringResourceLoader
velocimacro.max.depth
programmatic inclusion of macro libraries
can now call fixed-length list methods on arrays
$velocityHasNext for #foreach loops
configurable connection timeout for URLResourceLoader
Uberspect chainability and link-ability
consistent, correct line numbers and macro/template stacks in logs  
and

exceptions



-
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]

Re: [VOTE] Release VelocityTools 2.0-beta3

2008-12-01 Thread Geir Magnusson Jr.


+1

(And don't end it early even w/ 3 +1s  :)

geir

On Nov 30, 2008, at 5:21 PM, Nathan Bubna wrote:

Ok, Will said the new test build works for him; it is still  
available here:

http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/

Please vote regarding your support for releasing this new test build  
as

VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close time as
roughly 2pm PST on Wednesday, Dec 3.  Though if i get 3 +1s before
then, i'll end it early.  It's just a beta, after all. :)

My vote is, again, +1

On Sun, Nov 30, 2008 at 9:01 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:
Ok, i've accepted Will's veto and am changing my vote to -1, so  
here's

the result for the record:

-1
Nathan Bubna
Will Glass-Husain

On Sun, Nov 30, 2008 at 7:49 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:
Thanks, Will.  I actually feel like Adrian (or someone) reported  
this

too, but i forgot about it, since it's been working fine for me.
Well, i'll scrap this one and try to fix that.  I guess this won't  
be

going out in the same site update as Velocity Engine 1.6.

On Sat, Nov 29, 2008 at 9:38 PM, Will Glass-Husain
[EMAIL PROTECTED] wrote:

-1. Doesn't build.  see error report below.

WILL


C:\Documents and Settings\wglass\Desktop\velocity-tools-2.0-beta3- 
srcant

Buildfile: build.xml

clean:
 [delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
 [delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

clean-examples:

simple-example:

example-clean:

showcase-example:

example-clean:

struts-example:

example-clean:

test.clean:

prepare.compile:
  [mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
  [mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build\classes
  [mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

base-download:

commons-collections-download:

http-m1-download:

do-http-m1-download:
[get] Getting:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jar
[get] To: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib\commons- 
collections-3.2.jar

[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Can't get
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jarto
C:\Doc
uments and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib\commons- 
collections-3.2.jar


BUILD FAILED
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build.xml: 
104: The

following error occurred while executing
this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\download.xml: 
40: The

following error occurred while executin
g this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\download.xml: 
209: The

following error occurred while executi
ng this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\download.xml: 
121: The

following error occurred while executi
ng this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\download.xml: 
132: Can't

get http://mirrors.ibiblio.org/pub/m
irrors/maven2/commons-collections/jars/commons- 
collections-3.2.jar to

C:\Documents and Settings\wglass\Desktop\velocity-tools-2.0-
beta3-src\lib\commons-collections-3.2.jar

Total time: 1 second




On Fri, Nov 28, 2008 at 7:08 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:



Ok, there were no complaints about the current test build, so i'm
moving on to a vote.

The test build is still available here:
http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/http://people.apache.org/%7Enbubna/velocity/tools/2.0-beta3/ 



Please vote regarding your support for releasing this new test  
build as

VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close time as
roughly 7am PST on Monday, Dec 1st.  If the vote passes, I'll push
this to the mirrors and change the web site and get Henning to  
deploy it.

With luck i'll be able to announce it by Wed.

On Fri, Nov 21, 2008 at 12:02 PM,

Re: [VOTE] Release VelocityTools 2.0-beta3

2008-12-01 Thread Geir Magnusson Jr.

I think that the more the merrier on things like this for purposes of  
participation, and in addition,  someone might find something and vote  
-1 and be convincing in their argument.



On Dec 1, 2008, at 10:21 AM, Nathan Bubna wrote:


why not end early?  :(  i did the initial CFV 72+ hrs ago and only
changed one source file between the initial and secondary votes, and
we have a quorum and clear majority in favor of this beta release.  in
fact, there's only one active PMC member who hasn't yet voted +1 on
this, Claude.  If you are giving essentially a -1 to this procedural
change, i'd appreciate a good reason at the least.

On Mon, Dec 1, 2008 at 1:26 AM, Geir Magnusson Jr. [EMAIL PROTECTED]  
wrote:

+1

(And don't end it early even w/ 3 +1s  :)

geir

On Nov 30, 2008, at 5:21 PM, Nathan Bubna wrote:

Ok, Will said the new test build works for him; it is still  
available

here:
http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/

Please vote regarding your support for releasing this new test  
build as

VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close time as
roughly 2pm PST on Wednesday, Dec 3.  Though if i get 3 +1s before
then, i'll end it early.  It's just a beta, after all. :)

My vote is, again, +1

On Sun, Nov 30, 2008 at 9:01 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:


Ok, i've accepted Will's veto and am changing my vote to -1, so  
here's

the result for the record:

-1
Nathan Bubna
Will Glass-Husain

On Sun, Nov 30, 2008 at 7:49 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:


Thanks, Will.  I actually feel like Adrian (or someone) reported  
this

too, but i forgot about it, since it's been working fine for me.
Well, i'll scrap this one and try to fix that.  I guess this  
won't be

going out in the same site update as Velocity Engine 1.6.

On Sat, Nov 29, 2008 at 9:38 PM, Will Glass-Husain
[EMAIL PROTECTED] wrote:


-1. Doesn't build.  see error report below.

WILL


C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-srcant
Buildfile: build.xml

clean:
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

clean-examples:

simple-example:

example-clean:

showcase-example:

example-clean:

struts-example:

example-clean:

test.clean:

prepare.compile:
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build 
\classes

[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

base-download:

commons-collections-download:

http-m1-download:

do-http-m1-download:
  [get] Getting:

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jar
  [get] To: C:\Documents and

Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar

  [get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
  [get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
  [get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
  [get] Can't get

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jarto
C:\Doc
uments and

Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar


BUILD FAILED
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build.xml: 
104: The

following error occurred while executing
this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:40:

The
following error occurred while executin
g this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:209:

The
following error occurred while executi
ng this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:121:

The
following error occurred while executi
ng this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:132:

Can't
get http://mirrors.ibiblio.org/pub/m
irrors/maven2/commons-collections/jars/commons- 
collections-3.2.jar to

C:\Documents and Settings\wglass\Desktop\velocity-tools-2.0-
beta3-src\lib\commons-collections-3.2.jar

Total time: 1 second




On Fri, Nov 28, 2008 at 7:08 AM, Nathan Bubna  
[EMAIL PROTECTED] wrote:


Ok, there were no complaints about the current test build, so  
i'm

moving

Re: [VOTE] Release VelocityTools 2.0-beta3

2008-12-01 Thread Geir Magnusson Jr.

how does letting the vote run the full 3 days vs cutting it off early  
affect the site?


geir

On Dec 1, 2008, at 6:09 PM, Nathan Bubna wrote:


I fully agree, but we've already had more time than usual for
participation and testing already.  The first test build was 9 days
ago.  The first CFV was over 3 days ago.  The odds of what you
describe seem low, and the cost would be two separate site updates,
for which have high odds of being the greater trouble.

On Mon, Dec 1, 2008 at 2:58 PM, Geir Magnusson Jr. [EMAIL PROTECTED]  
wrote:

I think that the more the merrier on things like this for purposes of
participation, and in addition,  someone might find something and  
vote -1

and be convincing in their argument.


On Dec 1, 2008, at 10:21 AM, Nathan Bubna wrote:


why not end early?  :(  i did the initial CFV 72+ hrs ago and only
changed one source file between the initial and secondary votes, and
we have a quorum and clear majority in favor of this beta  
release.  in

fact, there's only one active PMC member who hasn't yet voted +1 on
this, Claude.  If you are giving essentially a -1 to this procedural
change, i'd appreciate a good reason at the least.

On Mon, Dec 1, 2008 at 1:26 AM, Geir Magnusson Jr.  
[EMAIL PROTECTED] wrote:


+1

(And don't end it early even w/ 3 +1s  :)

geir

On Nov 30, 2008, at 5:21 PM, Nathan Bubna wrote:

Ok, Will said the new test build works for him; it is still  
available

here:
http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/

Please vote regarding your support for releasing this new test  
build as

VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close time as
roughly 2pm PST on Wednesday, Dec 3.  Though if i get 3 +1s before
then, i'll end it early.  It's just a beta, after all. :)

My vote is, again, +1

On Sun, Nov 30, 2008 at 9:01 AM, Nathan Bubna [EMAIL PROTECTED]  
wrote:


Ok, i've accepted Will's veto and am changing my vote to -1, so  
here's

the result for the record:

-1
Nathan Bubna
Will Glass-Husain

On Sun, Nov 30, 2008 at 7:49 AM, Nathan Bubna  
[EMAIL PROTECTED] wrote:


Thanks, Will.  I actually feel like Adrian (or someone)  
reported this

too, but i forgot about it, since it's been working fine for me.
Well, i'll scrap this one and try to fix that.  I guess this  
won't be

going out in the same site update as Velocity Engine 1.6.

On Sat, Nov 29, 2008 at 9:38 PM, Will Glass-Husain
[EMAIL PROTECTED] wrote:


-1. Doesn't build.  see error report below.

WILL


C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-srcant
Buildfile: build.xml

clean:
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

clean-examples:

simple-example:

example-clean:

showcase-example:

example-clean:

struts-example:

example-clean:

test.clean:

prepare.compile:
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build 
\classes

[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

base-download:

commons-collections-download:

http-m1-download:

do-http-m1-download:
[get] Getting:


http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jar
[get] To: C:\Documents and


Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar

[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection java.io.FileNotFoundException:
http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Can't get


http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jarto
C:\Doc
uments and


Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar


BUILD FAILED
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\build.xml:104:

The
following error occurred while executing
this line:
C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:40:

The
following error occurred while executin
g this line:
C:\Documents and

Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:209:

The
following error occurred while executi
ng this line:
C:\Documents and

Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\download.xml:121:

The
following

Re: [VOTE] Release VelocityTools 2.0-beta3

2008-12-01 Thread Geir Magnusson Jr.


we all know why

On Dec 1, 2008, at 6:27 PM, Nathan Bubna wrote:


and Henning for that matter, since lately i have had to resort to
asking him to do it after several fruitless attempts.

On Mon, Dec 1, 2008 at 3:26 PM, Nathan Bubna [EMAIL PROTECTED] wrote:

i have to get the velocity-site stuff (home page, download page, etc)
updated for every release i do.  if the Tools 2.0-beta3 release
happens pretty much the same time as Engine 1.6, then i only have to
update the site once for both.  saves me some headache.

On Mon, Dec 1, 2008 at 3:22 PM, Geir Magnusson Jr. [EMAIL PROTECTED]  
wrote:
how does letting the vote run the full 3 days vs cutting it off  
early affect

the site?

geir

On Dec 1, 2008, at 6:09 PM, Nathan Bubna wrote:


I fully agree, but we've already had more time than usual for
participation and testing already.  The first test build was 9 days
ago.  The first CFV was over 3 days ago.  The odds of what you
describe seem low, and the cost would be two separate site updates,
for which have high odds of being the greater trouble.

On Mon, Dec 1, 2008 at 2:58 PM, Geir Magnusson Jr.  
[EMAIL PROTECTED] wrote:


I think that the more the merrier on things like this for  
purposes of
participation, and in addition,  someone might find something  
and vote -1

and be convincing in their argument.


On Dec 1, 2008, at 10:21 AM, Nathan Bubna wrote:

why not end early?  :(  i did the initial CFV 72+ hrs ago and  
only
changed one source file between the initial and secondary  
votes, and
we have a quorum and clear majority in favor of this beta  
release.  in
fact, there's only one active PMC member who hasn't yet voted  
+1 on
this, Claude.  If you are giving essentially a -1 to this  
procedural

change, i'd appreciate a good reason at the least.

On Mon, Dec 1, 2008 at 1:26 AM, Geir Magnusson Jr. [EMAIL PROTECTED] 


wrote:


+1

(And don't end it early even w/ 3 +1s  :)

geir

On Nov 30, 2008, at 5:21 PM, Nathan Bubna wrote:

Ok, Will said the new test build works for him; it is still  
available

here:
http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/

Please vote regarding your support for releasing this new  
test build

as
VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close  
time as
roughly 2pm PST on Wednesday, Dec 3.  Though if i get 3 +1s  
before

then, i'll end it early.  It's just a beta, after all. :)

My vote is, again, +1

On Sun, Nov 30, 2008 at 9:01 AM, Nathan Bubna  
[EMAIL PROTECTED]

wrote:


Ok, i've accepted Will's veto and am changing my vote to -1,  
so

here's
the result for the record:

-1
Nathan Bubna
Will Glass-Husain

On Sun, Nov 30, 2008 at 7:49 AM, Nathan Bubna [EMAIL PROTECTED] 


wrote:


Thanks, Will.  I actually feel like Adrian (or someone)  
reported

this
too, but i forgot about it, since it's been working fine  
for me.
Well, i'll scrap this one and try to fix that.  I guess  
this won't

be
going out in the same site update as Velocity Engine 1.6.

On Sat, Nov 29, 2008 at 9:38 PM, Will Glass-Husain
[EMAIL PROTECTED] wrote:


-1. Doesn't build.  see error report below.

WILL


C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-srcant
Buildfile: build.xml

clean:
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

clean-examples:

simple-example:

example-clean:

showcase-example:

example-clean:

struts-example:

example-clean:

test.clean:

prepare.compile:
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build 
\classes

[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

base-download:

commons-collections-download:

http-m1-download:

do-http-m1-download:
[get] Getting:



http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jar
[get] To: C:\Documents and



Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar
[get] Error opening connection  
java.io.FileNotFoundException:

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection  
java.io.FileNotFoundException:

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error opening connection  
java.io.FileNotFoundException:

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Can't get



http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jarto
C:\Doc
uments and



Settings

Re: [VOTE] Release VelocityTools 2.0-beta3

2008-12-01 Thread Geir Magnusson Jr.


anyone left to vote?

On Dec 1, 2008, at 6:32 PM, Nathan Bubna wrote:


ok, we've had this conversation, but until someone takes the time to
remedy that situation (one way or another), it is how it is.  so what
say you?  shall we wait two more days to make it a total of five for
voting and 11 for testing, or should we call this beta vote closed and
release the darn thing?

On Mon, Dec 1, 2008 at 3:28 PM, Geir Magnusson Jr. [EMAIL PROTECTED]  
wrote:

we all know why

On Dec 1, 2008, at 6:27 PM, Nathan Bubna wrote:


and Henning for that matter, since lately i have had to resort to
asking him to do it after several fruitless attempts.

On Mon, Dec 1, 2008 at 3:26 PM, Nathan Bubna [EMAIL PROTECTED]  
wrote:


i have to get the velocity-site stuff (home page, download page,  
etc)

updated for every release i do.  if the Tools 2.0-beta3 release
happens pretty much the same time as Engine 1.6, then i only have  
to

update the site once for both.  saves me some headache.

On Mon, Dec 1, 2008 at 3:22 PM, Geir Magnusson Jr. [EMAIL PROTECTED]
wrote:


how does letting the vote run the full 3 days vs cutting it off  
early

affect
the site?

geir

On Dec 1, 2008, at 6:09 PM, Nathan Bubna wrote:


I fully agree, but we've already had more time than usual for
participation and testing already.  The first test build was 9  
days

ago.  The first CFV was over 3 days ago.  The odds of what you
describe seem low, and the cost would be two separate site  
updates,

for which have high odds of being the greater trouble.

On Mon, Dec 1, 2008 at 2:58 PM, Geir Magnusson Jr. [EMAIL PROTECTED] 


wrote:


I think that the more the merrier on things like this for  
purposes of
participation, and in addition,  someone might find something  
and vote

-1
and be convincing in their argument.


On Dec 1, 2008, at 10:21 AM, Nathan Bubna wrote:

why not end early?  :(  i did the initial CFV 72+ hrs ago and  
only
changed one source file between the initial and secondary  
votes, and
we have a quorum and clear majority in favor of this beta  
release.

in
fact, there's only one active PMC member who hasn't yet voted  
+1 on
this, Claude.  If you are giving essentially a -1 to this  
procedural

change, i'd appreciate a good reason at the least.

On Mon, Dec 1, 2008 at 1:26 AM, Geir Magnusson Jr. [EMAIL PROTECTED] 


wrote:


+1

(And don't end it early even w/ 3 +1s  :)

geir

On Nov 30, 2008, at 5:21 PM, Nathan Bubna wrote:


Ok, Will said the new test build works for him; it is still
available
here:
http://people.apache.org/~nbubna/velocity/tools/2.0-beta3/

Please vote regarding your support for releasing this new  
test

build
as
VelocityTools 2.0-beta3:

[ ] +1 Let's do it
[ ] +0 Have fun; i don't care.
[ ] -0  Not sure about this, but i won't stop you.
[ ] -1 No, because __

The voting period is typically 72 hours, putting its close  
time as
roughly 2pm PST on Wednesday, Dec 3.  Though if i get 3 +1s  
before

then, i'll end it early.  It's just a beta, after all. :)

My vote is, again, +1

On Sun, Nov 30, 2008 at 9:01 AM, Nathan Bubna [EMAIL PROTECTED] 


wrote:


Ok, i've accepted Will's veto and am changing my vote to  
-1, so

here's
the result for the record:

-1
Nathan Bubna
Will Glass-Husain

On Sun, Nov 30, 2008 at 7:49 AM, Nathan Bubna [EMAIL PROTECTED] 


wrote:


Thanks, Will.  I actually feel like Adrian (or someone)  
reported

this
too, but i forgot about it, since it's been working fine  
for me.
Well, i'll scrap this one and try to fix that.  I guess  
this

won't
be
going out in the same site update as Velocity Engine 1.6.

On Sat, Nov 29, 2008 at 9:38 PM, Will Glass-Husain
[EMAIL PROTECTED] wrote:


-1. Doesn't build.  see error report below.

WILL


C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-srcant
Buildfile: build.xml

clean:
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[delete] Deleting directory C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

clean-examples:

simple-example:

example-clean:

showcase-example:

example-clean:

struts-example:

example-clean:

test.clean:

prepare.compile:
[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\build
[mkdir] Created dir: C:\Documents and

Settings\wglass\Desktop\velocity-tools-2.0-beta3-src 
\build\classes

[mkdir] Created dir: C:\Documents and
Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\dist

base-download:

commons-collections-download:

http-m1-download:

do-http-m1-download:
[get] Getting:




http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collections/jars/commons-collections-3.2.jar
[get] To: C:\Documents and




Settings\wglass\Desktop\velocity-tools-2.0-beta3-src\lib 
\commons-collections-3.2.jar
[get] Error opening connection  
java.io.FileNotFoundException:

http://mirrors.ibiblio.org/pub/mirrors/maven2/commons-collecti
ons/jars/commons-collections-3.2.jar
[get] Error

Re: What is schmoo

2008-10-06 Thread Geir Magnusson Jr.


:)

just text to be rendered as is

geir

On Oct 6, 2008, at 1:49 PM, Byron Foster wrote:


What is this term 'schmoo' I see in the code comments? as in:

/*
* if this reference is escaped (\$foo) then we want to do one of two
* things : 1) if this is a reference in the context, then we want to
* print $foo 2) if not, then \$foo (its considered schmoo, not VTL)
*/


-
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]

Re: Call a velocity macro

2008-03-10 Thread Geir Magnusson Jr.


Steven,

Don't judge this community by this thread - we have a long history of  
constructive and positive collaborative development.  Give it another  
chance.


geir

On Mar 10, 2008, at 8:05 AM, Yates Family wrote:

I take my hat off to all current, previous and prospective OS  
developers.
Clearly without the collective input and ideas this developer  
community

contributes to projects such as Velocity, software development as a
respected profession will struggle to earn a reputation as an  
innovative

vehicle which drives results.

I joined this mailing list in the hope I would gain access to a bank  
of
experienced developers by which of course I could draw on and  
develop my own
skills and techniques. After reading these posts, I am not convinced  
these

mailing lists are an appropriate tool which facilitates active and
constructive participation. I will not be recommending this to my
professional colleagues within the industry.

Many Thanks
Steven Yates

-Original Message-
From: Daniel Dekany [mailto:[EMAIL PROTECTED]
Sent: Monday, 10 March 2008 3:51 PM
To: Velocity Developers List
Subject: Re: Call a velocity macro

:D Hilarious! I mean, everybody knows Jonathan is an ass hole for his
doing this aggressive advertising here, and I told him back then for
several occasions to stop it (I'm a FreeMarker contributor... coming
from the side of the SATAN grunting/, you know), but what he brings
out of you guys worths all the face loss of the FM project. :) I
understand that ass licking and being Politically Correct and things
like that are very important for being professional, means, for a
good career. I can handle that, life is that disgusting and cruel,
etc... I shut my trap at may employees as well, and of course I LOVE
THEM ;), who ever they are. If they think that brings them the income,
so be it. But, sometimes I have the feeling that some of you are not
just pretending these things for practical considerations, but you
indeed think it seriously! And that's creepy. Since when should people
respect things that are bad, and since when it's not professional to
call the sh*t to what it is? Especially in private??? Come on! I have
to puke from all of this liberal bullshit when someone honestly
believes these. How can someone be such a... eh. And then you felt you
have to report it on the list, or what was that??? And then... this
When Nathan Bubna wrote me... I know it's not the same case, but I
can't help but remember when on another ASF list I was critical about
a certain technical aspect of a project, in a *professional* but
surely firm way, and another user started to discuss the stuff with me
as opposed to trying to gently ridicule the issue. And later he wrote
me in private, that he wont continue, because his employer, whose
company was connected with some key personal at the ASF project, was
told him that, well, it was a wrong thing that he has talked to me. He
was almost angry with me because I got him into trouble. God... You
see, poor guy was all time there on the list, but he didn't realize I
was internally declared to be persona non garta (it seems...), and he
talked to me! What a mistake! :)


Monday, March 10, 2008, 3:46:39 AM, Adrian Tarau wrote:


Jonathan,

I must confess you are above my expectations/past experiences. When
I post your nice words on the mailing list(development list by the
way) I didn't knew who you are. I thought you are just a regular
user(or even a FreeMarker commiter) who is way to passionate about
FreeMarker and tries to trash the Velocity name just because he had  
a bad

experience with Velocity.

When Nathan Bubna wrote me and told me who you are, I realized I
just started some old war between Velocity and FreeMarker(after I
read some of your old posts).So there was not my intention to trash
the FreeMarker lead developer name because *I didn't knew who you  
are*.


World like dipshit, despicable, don't sit very well near lead
developer or even software engineer. I would expect something
like this in a bar, but not on a mailing list.

Reading your last post, I realized you don't get it and probably
you don't understand the concept. !!!IT'S ALL ABOUT RESPECT!!!.
I don't care how many bad designs or weak points has Velocity, you
should treat the Velocity community, the current developers, past
and current owners with RESPECT. Jonathan , there are other ways to
bring new users to FreeMarker...your way is completely wrong.

You, as a (past) Velocity user are entitled to wrote about your bad
experiences with Velocity and thanks to the current search engines
your words will be visible in the first 100 results in any search
engine. If the Velocity developers won't take action to improve the
engine and all those bad experiences will pile up, Velocity will die
by itself, you don't need to help it. Or you could help, but do it  
in a

different way.


Try to get this and you will sleep better.

-Original Message-
From: news [mailto:[EMAIL PROTECTED]

Re: Call a velocity macro

2008-03-09 Thread Geir Magnusson Jr.


Jonathan,

Knock it off.

It's 2008.  You've been unsuccessfully charging this windmill for 7 or  
8 years now, and you still can't remain civil in a conversation.


Go away, please.

geir


On Mar 9, 2008, at 1:21 PM, Jonathan Revusky wrote:


Adrian Tarau wrote:

Jonathan,
Basic common sense? Based on your long posts on Velocity forum, I  
think I can ask you if you have some common sense.


Adrian, you little dipshit, whatever long posts I wrote on this  
forum were responses to other public posts on the forum. I wrote you  
a note in private and you responded on the public forum. That is the  
violation of nettiquette I am referring to. If you don't understand  
that you are not supposed to do that, as I said before, you don't  
understand much.


Well, it's not just that, Adrian. You're such a despicable  
hypocrite. I mean, why did you respond in public to a private note?  
Obviously to try to goad me into starting some kind of flame war or  
whatever. You try to goad somebody into responding and then you say  
tsk tsk, look what a bad guy you are.


Typical stuff, but it's pathetic. I mean, you're pathetic, Adrian.

If you really think Velocity is a dinosaur, you could let him  
die(with some respect if you say it meant something 7 years ago).


7 years ago (maybe closer to 8 years ago) Velocity was written by  
Jon Monkey see, Monkey do Stevens as a copycat clone of an  
existing open source project called WebMacro. It was such a mindless  
copycat job that he even copied some rather strange limitations of  
WebMacro. One such thing was that WebMacro had no support for  
decimal numbers, only integers, probably because the original author  
had not got round to implementing it. You know, really, it's just  
like a dim student who copies another student's exam answers word  
for word, including the spelling mistakes.


The really humorous thing about this is that, at a later stage, when  
people showed up who obviously needed decimal numbers, Velocity  
maintainers (rather than just implementing decimal number support)  
spent all kinds of energy arguing that the lack of decimal numbers  
in Velocity was the result of some kind of profound philosophical  
thinking on their part,.. yeah, like they'd really thought about it  
and decided that integers were good, but decimal numbers bad. Of  
course, everybody who knew the history of the project knew that  
Velocity lacked decimal number support because it was a mindless  
copy of Webmacro, which in turn lacked decimal number support.


In any case, do you think that's really a very nice thing to do? You  
write a mindless copy of somebody else's work and then you use the  
apache.org projection to eclipse the original pioneering work? It's  
the kind of thing Microsoft historically does, but at least that's  
to make money, so it makes sense. The origins of the Velocity  
project really are in behavior that is somewhat pathological.


I mean, how would you feel about this if you were the original  
author of WebMacro? It's really not very nice. These really aren't  
very nice people.


Now, to be fair, all the original authors of Velocity, anybody who  
designed or implemented any significant part of the codebase, are  
long gone. What you have now is a set of poeple who have taken on  
the role of being owners of the project, because it's some kind of  
feather in their cap or something. But really, if you really look at  
it, what they're doing is totally masturbatory, putting out  
infinitesimal incremental releases of a product that is 6 years  
behind the state of the art in its space.


And again, aside from being rather pathetic, is that really a very  
nice thing to be doing? I mean, the problem is that a lot of people  
in this field are pressed for time and cannot evaluate everything  
properly, so many people see something is on apache.org, and they  
reason, okay, I'm using the Apache Web Server, or I'm using tomcat,  
so it makes sense to use the templating engine that comes from  
apache. So this, and basically anything on apache.org, gets a level  
of attention and usage totally out of proportion to its technical  
merit. So, you can see why people would end up thinking that  
Velocity is a reasonable option and use it.


The problem is, of course, that, eventually many people end up  
realizing waht's up with this. Consider what Max Andersen is saying  
in this blog entry: http://in.relation.to/Bloggers/AStoryAboutFreeMarkerAndVelocity

Here is a quote:

The choice originally fell on Velocity since it was the biggest  
player around, and I added it naively thinking that the error and  
log handling could not be that bad if so many people were using it  
and if there were an issue it would be fixed soon. As time went by I  
learned that it was definitely not the case.


He's openly saying that he didn't research the alternatives, because  
it was highly visible and he figured it couldn't be that bad (though  
he later learns it is...

Re: Call a velocity macro

2008-02-21 Thread Geir Magnusson Jr.


Wait - that's not true You certainly can do scoped velocimacros...

geir

On Feb 21, 2008, at 12:57 PM, Nathan Bubna wrote:


On Thu, Feb 21, 2008 at 6:36 AM, Christopher Schultz
[EMAIL PROTECTED] wrote:

Nathan,


Nathan Bubna wrote:
I'm pretty sure #local is still just in Geir's whiteboard  
section.  No
one has ever gotten it promoted out of there.  I've never been  
opposed
to it, but i've also never been interested in putting the work  
needed

into it (tests, docs, etc).


I have to admit that when I started really writing macros (other than
super simple ones), I was disappointed to learn that there was no
stack... that is, I couldn't implement certain things properly  
using

the macro facility because recursive calls would overwrite variables
from what I would have considered outer scopes.

If anyone is contemplating a Velocity 2.x, I would seriously  
recommend

that macros and other things (like #parse, #evaluate, and similar
things) run in their own, local and inherited contexts. This gives  
much

greater freedom to the developer, who doesn't have to worry about
temporary variables within macros, etc. clobbering variables set in
the caller's scope.

It would be best if this were simply a language feature, instead of a
hack provided through another directive (though it would have to be
hacked in this way for Velocity 1.x, since some folks may actually  
rely

on this inconvenient setup.


inconvenience is sometimes a matter of perspective, and you might soon
find people providing special #setglobal hacks for when they do want
to clobber a variable in the caller's scope.   personally, i've always
been able to see this both ways and never had much trouble adjusting
to the lack of scoping.  when my macros/layouts/parses ever get
complicated enough that i can't track all the variables, i just start
namespacing ones i want to keep 'local'.

anyway, being able to see both sides and easily adjust either way, you
probably won't ever find me motivated to work on this or object to
anyone else working to change this in a theoretical 2.x version.
namespaces or scoping, i'm good either way. :)


-chris




-
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]

Re: Call a velocity macro

2008-02-20 Thread Geir Magnusson Jr.

There was something really sucky about it, which is why I didn't move  
it forward.  I forget why it was bad...


geir

On Feb 20, 2008, at 5:16 PM, Nathan Bubna wrote:


I'm pretty sure #local is still just in Geir's whiteboard section.  No
one has ever gotten it promoted out of there.  I've never been opposed
to it, but i've also never been interested in putting the work needed
into it (tests, docs, etc).

http://svn.apache.org/repos/asf/velocity/engine/trunk/whiteboard/geir/Local.java

On Wed, Feb 20, 2008 at 2:09 PM, Adrian Tarau  
[EMAIL PROTECTED] wrote:

Thanks,

I think I will implement a different directive, based on #parse but
passing the parameters  having all the variables local to the  
function.

I'm not aware of any directive called #local. What do you mean?



[EMAIL PROTECTED] wrote:

Hi Adrian,

in a similar scenario I use the #parse directive and placed the code
snippets (aka. macros) into a *.vtl file each. Something like:

#set( $component = ... )
#set( $type = $component.type )
#parse(renderComponent${type}.vtl )

This has the advantage, that these rendering Templates parsed once  
and

cached.

The downside is that the parameter passing is implicit (here
$component is the input parameter for the parsed template) and that
these parsed templates must be careful not to overwrite existing
variables. For this I used a different namespace (postfixed  
variables

with _), but you can also use the new #local directive to avoid
conflicts.

Cheers,
Christoph

Adrian Tarau wrote:
I've always imagined a macro as a function, but as the name says,  
the
macro body is expanded at parsing time in the current template.  
This

has the advantage to have the template tree in memory and the
rendering speed is the fastest possible.

What I need is more like calling a template as a function(which
behave like a function) in the context of the current execution
context(same context, same writer) without too much overhead.

I will try to implement something like that and I will publish the
result, maybe it will be useful for somebody else.

Thanks.

Massip, Etienne wrote:

A dynamic call of a parameter-given name is a minimal parsing, but
still is, preventing any kind of compile-time linkage from being
done.

The expression seems to be known only at template-parsing-time,
isn't it ?

I think

#call('render'+$component.type $component)

makes very little difference with

#evaluate('#render' + $component.type + '($component)')

If the evaluate directive really performs poorly, then maybe it
should be a good idea to speed it up other than create a new and
specialized one ?

-Message d'origine-
De : Adrian Tarau [mailto:[EMAIL PROTECTED] Envoyé : mardi  
19

février 2008 16:14
À : Velocity Developers List
Objet : Re: Call a velocity macro

Velocity.evaluate or Velocity.invokeVelocimacro(which calls
evaluate) doesn't provide support to pass objects as parameters  
and

is not suitable to be called from a template.

The new directive #evaluate is actually Velocity.evaluate.  It is
still an evaluate, which means expression parsing. I would like to
avoid that. If you will call call/invoke directive too often I
think it will perform badly, due the fact that a parsing step is
performed.

In this case, a call to a velocity macro, we don't need the  
parsing

step. We know the expression, and what we need is to prepare the
node without parsing.I don't know much about the velocity  
internals,

but I presume it should be possible.
And I think such a directive should be part of the core, I mean it
will be easy to implement a switch(is what I need actually)  
based

on some variable. Like in my case :

#macro(renderLabel $component)

#end

#macro(renderTextField $component)

#end

#macro(renderRadioButton $component)

#end

.

#call('render'+$component.type $component)

where 'type' is 'label', 'text-field', 'radio-button'(of course
there is a normalization of the type value, first character upper
case, '-' makes the next character uppercase, etc).

Instead of lots of tests with #if, it will be better(and faster)  
to
have this 'switch'.At least it looks better, the template is  
cleaner

and it is (it will be)also faster.

Thanks.

   /Reader reader = *new* BufferedReader(*new*
StringReader(sourceText));
   String templateName = context.getCurrentTemplateName();
   SimpleNode nodeTree = *null*;

   *try*
   {
   *nodeTree* = rsvc.parse(reader, templateName);
   }
   *catch* (ParseException pex)
   {
    use the line/column from the template
   Info info = *new* Info( templateName, node.getLine(),
node.getColumn() );
   *throw*  *new* ParseErrorException( pex.getMessage(),
info );
   }
   *catch* (TemplateInitException pex)
   {
   Info info = *new* Info( templateName, node.getLine(),
node.getColumn() );
   *throw*  *new* ParseErrorException( pex.getMessage(),
info );
   }/



Massip, Etienne wrote:

Re: svn commit: r579331 - in /velocity/engine/trunk/src: java/org/apache/velocity/util/introspection/UberspectImpl.java test/org/apache/velocity/test/ForeachTestCase.java

2007-09-25 Thread Geir Magnusson Jr.

what if it returns something you can't iterate over?  Maybe check the  
return type first?


geir

On Sep 25, 2007, at 4:22 PM, Nathan Bubna wrote:


On 9/25/07, Will Glass-Husain [EMAIL PROTECTED] wrote:

Wow, Nathan -- you are on a tear.  Nice work.


well, i found a little time to work on some of these nagging little  
things.  :)



WILL

On 9/25/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Author: nbubna
Date: Tue Sep 25 10:59:43 2007
New Revision: 579331

URL: http://svn.apache.org/viewvc?rev=579331view=rev
Log:
support any object with an iterator() method in #foreach  
(VELOCITY-443)


Modified:

velocity/engine/trunk/src/java/org/apache/velocity/util/ 
introspection/UberspectImpl.java


velocity/engine/trunk/src/test/org/apache/velocity/test/ 
ForeachTestCase.java


Modified:
velocity/engine/trunk/src/java/org/apache/velocity/util/ 
introspection/UberspectImpl.java

URL:
http://svn.apache.org/viewvc/velocity/engine/trunk/src/java/org/ 
apache/velocity/util/introspection/UberspectImpl.java? 
rev=579331r1=579330r2=579331view=diff


 
==

---
velocity/engine/trunk/src/java/org/apache/velocity/util/ 
introspection/UberspectImpl.java

(original)
+++
velocity/engine/trunk/src/java/org/apache/velocity/util/ 
introspection/UberspectImpl.java

Tue Sep 25 10:59:43 2007
@@ -139,6 +139,22 @@
 }
 return new EnumerationIterator((Enumeration) obj);
 }
+else
+{
+// look for an iterator() method to support the JDK5  
Iterable
+// interface or any user tools/DTOs that want to  
work in
+// foreach without implementing the Collection  
interface

+Class type = obj.getClass();
+try
+{
+Method iter = type.getMethod(iterator, null);
+return (Iterator)iter.invoke(obj, null);
+}
+catch (NoSuchMethodException nsme)
+{
+// eat this one, but let all other exceptions thru
+}
+}

 /*  we have no clue what this is  */
 log.error(Could not determine type of iterator in  
#foreach loop

at  + i);

Modified:
velocity/engine/trunk/src/test/org/apache/velocity/test/ 
ForeachTestCase.java

URL:
http://svn.apache.org/viewvc/velocity/engine/trunk/src/test/org/ 
apache/velocity/test/ForeachTestCase.java? 
rev=579331r1=579330r2=579331view=diff


 
==

---
velocity/engine/trunk/src/test/org/apache/velocity/test/ 
ForeachTestCase.java

(original)
+++
velocity/engine/trunk/src/test/org/apache/velocity/test/ 
ForeachTestCase.java

Tue Sep 25 10:59:43 2007
@@ -21,6 +21,7 @@

import java.io.StringWriter;
import java.util.ArrayList;
+import java.util.Iterator;
import java.util.List;

import junit.framework.TestCase;
@@ -75,10 +76,10 @@
 }

 /**
- * Tests proper method execution during a Foreach loop with  
items

- * of varying classes.
+ * Tests proper method execution during a Foreach loop over a
Collection
+ * with items of varying classes.
  */
-public void testMethodCall()
+public void testCollectionAndMethodCall()
 throws Exception
 {
 List col = new ArrayList();
@@ -94,4 +95,41 @@
 assertEquals(Method calls while looping over varying  
classes

failed,
  int 100 str STRVALUE , writer.toString());
 }
+
+/**
+ * Tests that #foreach will be able to retrieve an iterator  
from
+ * an arbitrary object that happens to have an iterator()  
method.

+ * (With the side effect of supporting the new Java 5 Iterable
interface)
+ */
+public void testObjectWithIteratorMethod()
+throws Exception
+{
+context.put(iterable, new MyIterable());
+
+StringWriter writer = new StringWriter();
+String template = #foreach ($i in $iterable)$i #end;
+Velocity.evaluate(context, writer, test, template);
+assertEquals(Failed to call iterator() method,
+ 1 2 3 , writer.toString());
+}
+
+
+public static class MyIterable
+{
+private List foo;
+
+public MyIterable()
+{
+foo = new ArrayList();
+foo.add(new Integer(1));
+foo.add(new Long(2));
+foo.add(3);
+}
+
+public Iterator iterator()
+{
+return foo.iterator();
+}
+}
+
}






--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com



-
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]

Re: DVSL

2007-05-12 Thread Geir Magnusson Jr.



On May 12, 2007, at 6:03 PM, Claude Brisson wrote:


Hi.

DVSL a small and simple project that slept for quite a long time  
but it

can be quite handy for small XML transformation tasks. I think it
deserves at least a 1.0 release.


Me too!



Since nobody is handling this project, and since I used at least some
times in the past (and may use it again), I'm gonna take a look at  
it to

see if the few JIRA issues can be resolved so that we can release it.


Go for it!




  Claude


-
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]

Re: [Fwd: Incubation of the Click Project at the Apache Software Foundation]

2007-04-06 Thread Geir Magnusson Jr.


yeah, sorry - I have zero time right now...

On Apr 6, 2007, at 11:20 AM, Henning Schmiedehausen wrote:


Hi,

thanks. According to the current discussion on [EMAIL PROTECTED], it
seems that actually all mentors must be members. As Daniel and Geir  
are

currently probably pretty busy, we will have to recruit someone from
outside Velocity to help.

Best regards
Henning



On Tue, 2007-04-03 at 15:57 -0700, Will Glass-Husain wrote:

I volunteer.  (and as you know, I'm an ASF member).

Will

On 4/3/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:


Hi,

that is really good news. Congratulations to the Click Community  
to be

willing to take this step!

Our next step will be now to start drafting up a proposal. I'd  
suggest

that we do so on the Velocity Wiki (unless Click has its own Wiki
somewhere).

As said before, I'd volunteer as Champion. We also need a number of
mentors (as I just got drafted into a proposal on the Incubator,  
three
seems to be a good number), of which one *must* be an ASF member.  
So we

need some volunteers here.

More later, I will have to read up on the exact rules myself. :-)

Best regards
Henning


On Fri, 2007-03-30 at 22:12 +1000, Malcolm Edgar wrote:

Hi All,

The Click move to Apache vote is in. We have a positive vote,  
with 1

abstention and 4 positive votes.

  [ 0 ]  Ahmed Mohombe

  [+1]  Malcolm Edgar

  [+1]  Bob Schellink

  [+1]  Stephen Haberman

  [+1]  Naoki Takezoe

So I would like to move forward to the Apache incubation process  
for

Click.


As I imagine the incubation process will take some time, I  
propose to
have a sourceforge Click 1.3 release, before an Apache Click  
release.


If the Apache migration is accepted, I don't think we should  
fork the
code base maintaining parallel sourceforge and apache branches,  
as the

overhead would be prohibitive.

regards Malcolm Edgar

--- 
--

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]








-
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]

Re: update on site issues

2007-02-10 Thread Geir Magnusson Jr.


Sorry - forgot the smiley :)

geir

On Feb 10, 2007, at 8:04 AM, Geir Magnusson Jr. wrote:



On Feb 9, 2007, at 6:45 PM, Nathan Bubna wrote:


Don't get too excited yet.

So, i gave up on trying to get the site plugin to generate the
index.html page with the news macro.  Instead, i commented out the
news macro and manually added the latest news.  So now i have the  
site

building and running perfectly on machine.

Now i'm caught up trying to deploy the site.  I've added my user/pass
to the velocity.apache.org server in my M2 settings.xml, but the
site:deploy target is failing rather mysteriously:

[INFO]  
- 
---

[INFO] Building Apache Velocity Site
[INFO]task-segment: [site:deploy]
[INFO]  
- 
---

[INFO] [site:deploy]
scpexe://people.apache.org/www/velocity.apache.org - Session: Opened
Executing command: ssh -o BatchMode yes [EMAIL PROTECTED]
mkdir -p /www/velocity.apache.org/.

Permission denied (publickey,keyboard-interactive).

scpexe://people.apache.org/www/velocity.apache.org - Session:  
Disconnecting
scpexe://people.apache.org/www/velocity.apache.org - Session:  
Disconnected
[INFO]  
- 
---

[ERROR] BUILD ERROR
[INFO]  
- 
---

[INFO] Error uploading site

Embedded error: Error performing commands for file transfer
Exit code 255 - Permission denied (publickey,keyboard-interactive).

[INFO]  
- 
---

[INFO] Total time: 16 seconds
[INFO] Finished at: Fri Feb 09 14:54:22 PST 2007
[INFO] Final Memory: 6M/12M
[INFO]  
- 
---


I've tried about a dozen different things messing with rsa and dsa
keys, adding/removing my password from settings.xml, and more, but no
luck yet.  I've also tried running the ssh command that is failing,
and it only works if i take out the -o BatchMode yes part.

Anyone have any ideas?


svn revert




On 2/9/07, Will Glass-Husain [EMAIL PROTECTED] wrote:

Good to hear!  Glad we have this as a group capability.

WILL

On 2/8/07, Nathan Bubna [EMAIL PROTECTED] wrote:
 I've made some progress with building the site.  I've managed  
to get
 maven (2.0.6-snapshot) to build the web site successfully on my  
local

 machine with the exception of the front page, which appears to be
 failing due to the following error:

 Caused by:  
org.apache.maven.doxia.macro.manager.MacroNotFoundException:

 Cannot find macro with id = null

 I'm hoping to look further into that today or tomorrow if i  
have time.

  I haven't tried deploying the site yet.

 In the meantime, i've also noticed that there are a number of  
folders

 in /www/velocity.apache.org/ that do not have velocity group
 permissions, so i can't do anything with them.  These are the  
engine/,
 tools/, and dvsl/ folders.  This means i can't add the  
documentation
 for the Tools 1.3 release or the devel/ documentation in their  
current

 location unless Henning checks this and changes the group perms or
 someone else with sufficient karma changes them.

 Anyone out there got that karma? Geir?  Or does anyone know who i
 should talk to?  I'm guessing the infrastructure people, but i  
thought

 i'd ask here first.

 The other option would be to change all those locations, but i'd
 rather not if it can be helped.

  
 
-

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




--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

 
-

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]




-
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]

Re: update on site issues

2007-02-08 Thread Geir Magnusson Jr.


I fixed the group.  You should be good to go.  If not, bellow again...

geir

On Feb 8, 2007, at 5:50 PM, Nathan Bubna wrote:


I've made some progress with building the site.  I've managed to get
maven (2.0.6-snapshot) to build the web site successfully on my local
machine with the exception of the front page, which appears to be
failing due to the following error:

Caused by:  
org.apache.maven.doxia.macro.manager.MacroNotFoundException:

Cannot find macro with id = null

I'm hoping to look further into that today or tomorrow if i have time.
I haven't tried deploying the site yet.

In the meantime, i've also noticed that there are a number of folders
in /www/velocity.apache.org/ that do not have velocity group
permissions, so i can't do anything with them.  These are the engine/,
tools/, and dvsl/ folders.  This means i can't add the documentation
for the Tools 1.3 release or the devel/ documentation in their current
location unless Henning checks this and changes the group perms or
someone else with sufficient karma changes them.

Anyone out there got that karma? Geir?  Or does anyone know who i
should talk to?  I'm guessing the infrastructure people, but i thought
i'd ask here first.

The other option would be to change all those locations, but i'd
rather not if it can be helped.

-
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]

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

2007-01-31 Thread Geir Magnusson Jr.



On Jan 31, 2007, at 10:09 AM, Henning P. Schmiedehausen wrote:


Geir Magnusson Jr. [EMAIL PROTECTED] writes:


because Maven2 has issues and that's what the current site is being
built with.  i've tried to get it working on my machine, but no luck
yet.



Then I'd argue this shouldn't be our site until this is fixed :)


Geir,

sorry for me starting to lose my patience here, but this is the thing:

Between November '06 and now I tried to make the new velocity project
site and the engine docs to be an as good user experience as can be.

I put a lot of work in this using maven. There have been a number of
things sprouted from here that you can review under site/tools. I also
found enough bugs in maven and its components to fill a small
folder. That is how open source works. Especially open source that
tries to be somewhat on the Leading wave.

Up until now, all you did was saying I don't like this. I'm
concerned about this. I'd argue that we do it differently.


I don't recall.  I'm usually not that prescient.



The thing is: That is not helping. Actually, it is frustrating in a
big way.

I'd like you to spent some time to take a look at what is there, not
what you would like to have (and then seem to expect to appear
automagically).


I didn't ask you to change anything, IIRC.


If you find things missing, being less than ideal, I'd
encourage you to either

a) fix it
b) open issues for it

Please review wheter doing neither a) nor b) but just leaning back and
saying I'd argue that this should not be our site until it is fixed
is really a constructive and encouraging way to work in a (regrettably
small) developer community.


Henning - what you are saying is that you broke it and you want me to  
fix it?  I'm not sure I like that.  I tend to believe that except  
when people agree to do the contrary, it's a good idea to ensure that  
any works-in-progress remain uncommitted, or in a branch or  
whiteboard, to ensure that there's a working configuration available  
to anyone to work with.


I haven't commented on the site, the quality of it or anything like  
that.  I simply noted surprise that we have a site that only you can  
build, and noted that maybe that shouldn't actually be the official  
project site until that's fixed.


geir



Best regards
Henning


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

-
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]

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

2007-01-30 Thread Geir Magnusson Jr.



On Jan 31, 2007, at 12:52 AM, Nathan Bubna wrote:


On 1/30/07, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:


On Jan 30, 2007, at 11:24 PM, Henning Schmiedehausen wrote:

...


 As a compromise, I'd like to propose to keep the 1.5 release and
 call it
 Release candidate in the same way as httpd calls it's releases  
x.y.z
 and assigns them levels of quality such as (Alpha) (Beta)  
(Release

 Candidate) (General Availability). So this would then be
 Velocity 1.5 (Release Candidate) with probably Velocity 1.5.1  
(General

 Availability) following.

No - that's confusing.  1.5 RC would be followed by 1.5 GA


eh.. only if we're talking about a vote to just re-label 1.5.  if we
make changes to the distro (even for docs) and roll a new release,


We didn't release this, so it doesn't matter, IMO.


then we need a new number.  since we're only talking about doc
changes, 1.5.1 seems appropriate and would be likely to get voted as
GA.

-
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]

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

2007-01-30 Thread Geir Magnusson Jr.



On Jan 31, 2007, at 1:52 AM, Will Glass-Husain wrote:


Hi,

Knew I'd be unpopular the moment I hit send.


You did the right thing.  This is what the oversight processes here  
at the ASF are about.




Three quick notes.

1) don't think the changes are big.  But I think the distro should be
reviewed and fixed.  A bad hyperlink on the main menu, in our first
release in 3 years, looks sloppy and conveys an inaccurate impression
of the quality of our product.

2) Unlike V-tools, we did not have a test build.  Instead, the final
package was created with the choice vote yes, or delay the release.
I don't like it.


That's why I advocate having no manual steps to re-create the  
release.  If you are lucky, you have everything happen in HEAD.   
Then, tag *that*, and do misc tweaks if needed.


Also, the vote or delay was simply due to special circumstances,  
not regular practice.





3) I'd be happy to vote +1 if we could call this Velocity 1.5rc1.  But
given the historic significance of this release, I urge us to release
Velocity 1.5 in a professional distro without obvious errors.(no
need to immediately issue Velocity 1.5.1).


I think an rc1 should be as perfect as much as possible as well -  
calling it RC means (to me) - this is what we'd like to release,  
anything obvious we missed? and engage the public on it.  That's  
what we used to do, IIRC, around here :)


So yeah, this could be RC1, but to do that, I'd prefer to see  
something sane done like


velocity/engine/branches/1.5
   tags/1.5RC1

and have that released w/ RC1 in the right places.  Then we wait  
until Henning gets back from lounging about for 6 weeks :) fix  
anything the community found, and go for 1.5


geir




best,
WILL



On 1/30/07, Nathan Bubna [EMAIL PROTECTED] wrote:

On 1/30/07, Will Glass-Husain [EMAIL PROTECTED] wrote:
 Hi all,

 Reluctantly, I vote -1.

:(

 I tested the release.  It compiled fine, ant test ran fine under  
JDK
 1.5 and 1.6, worked with Velocity Tools 1.2.  But when I checked  
all

 the hyperlinks, the anakia page was missing.  There's an error when
 generating the page and it was left out of the distribution [1].

C'mon.  Anakia's documentation is anything but hard to find.  I'm all
for getting things right, but not for holding back releases based on
one missing doc.  I'd rather you let Henning release 1.5 now and
release 1.5.1 yourself next week.

 I'm concerned about two things.  I'm concerned about a prominent  
bad
 link on the main menu, and I'm concerned the last minute vote  
on the
 final release might not have uncovered additional problems.   
We've a

 chance to make a major impression on the Java world with this
 prominent release and I want this to be very smooth installation  
for

 both new users and the typical existing user who wants to upgrade.

We can't cower in fear of unknown bugs.  Fix what you know and care
about, then let's get this thing moving again.

 My recommendation is to delay the release until there's time to fix
 these doc issues and for more thorough testing.  Mid-March seems  
fine.

  For the shallow bugs theory to work, we need to issue a release
 candidate that everyone can work with.  This doesn't need to be an
 actual release, just a binary distribution we can test.  After a  
few

 weeks we should be assured the details are 100% set.

How about two betas and a test build?  That's what we've had.  This
release has had much time to prepare.  More time won't kill us, but
let's not pretend things are ever likely to be 100% set.  Trust  
me, if

i cared enough, i could start combing thru the docs of almost any
major project you like and find dozens of errors.  Same goes for most
code.   Final releases will never be perfect, but the shallow bugs
theory won't work if we don't get *them* out there.  Far fewer people
bother with release candidates and betas.

 Incidentally, I disagree with Henning's comment that the beta2  
had no
 errors.  Actually, beta2 had a serious error in the build  
process in

 which ant test failed when run from the actual distribution.  It
 worked from the source distribution but not the released  
package.  No

 one found this problem for a month.

And it's fixed, is it not?

 I can't adequately express my admiration of Henning's efforts in  
the

 last 6 months to get this out. This must be frustrating.  I take
 responsibility myself for not thinking through the implications  
of the
 release process when Henning proposed a month ago we issue a  
release

 at the end of January.

Taking responsibility in the open source world means only one thing,
if you ask me.  Doing the work.  If you're going to take
responsibility for this by re-doing this whole process to your
satisfaction either by repeating the 1.5 test build and vote or by
letting 1.5 go and releasing a 1.5.1, then i won't protest.  But
please don't just sit back and critique at the last minute.   That's
not just frustrating, it's obnoxious.

 However, the

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

2007-01-30 Thread Geir Magnusson Jr.



On Jan 31, 2007, at 3:48 AM, Will Glass-Husain wrote:


I thought about this a little more.  There's a couple things we can do
that I'd support.

(1) Figure out a way to call this release something other than
Velocity 1.5, e.g. Velocity 1.5rc1 and issue the release immediately.
Can we do this without a 3 day vote?


See my other response.  Why the rush?  If Henning has to go vacation,  
then you do the RC1 stuff, and we'll wait until he gets back for the  
1.5 GA release.




(2) Take a little time to make the minor fix required, then release
the software.  I can step up to do this over the next few days.  I
think Henning was concerned we'd need to rebuild the site and he's the
only one that can do that.   If I managed the release, I'd probably
want to do Velocity 1.5rc1 first and then Velocity 1.5 two weeks
later.


Why is he the only one that can do the site?



(3) Henning remains release manager and we wait until March for the
release.  We could leave the VELOCITY_1.5_BRANCH up so that the
release is ready to go.  We can also direct users interested in 1.5
specific features to that svn branch.


Right.  Do the fixes in the branch, then make a

tag/1.5rc1

build, vote and release as RC1.

When Henning gets back, do 1.5 GA.  Advantage is that people get to  
beat 1.5RC1 about for a month.


geir



I'm sure our European community is long abed, I'll look for comments
from them in the morning.

WILL

On 1/30/07, Will Glass-Husain [EMAIL PROTECTED] wrote:

Hi,

Knew I'd be unpopular the moment I hit send.

Three quick notes.

1) don't think the changes are big.  But I think the distro should be
reviewed and fixed.  A bad hyperlink on the main menu, in our first
release in 3 years, looks sloppy and conveys an inaccurate impression
of the quality of our product.

2) Unlike V-tools, we did not have a test build.  Instead, the final
package was created with the choice vote yes, or delay the release.
I don't like it.

3) I'd be happy to vote +1 if we could call this Velocity 1.5rc1.   
But

given the historic significance of this release, I urge us to release
Velocity 1.5 in a professional distro without obvious errors. 
(no

need to immediately issue Velocity 1.5.1).

best,
WILL



On 1/30/07, Nathan Bubna [EMAIL PROTECTED] wrote:
 On 1/30/07, Will Glass-Husain [EMAIL PROTECTED] wrote:
  Hi all,
 
  Reluctantly, I vote -1.

 :(

  I tested the release.  It compiled fine, ant test ran fine  
under JDK
  1.5 and 1.6, worked with Velocity Tools 1.2.  But when I  
checked all
  the hyperlinks, the anakia page was missing.  There's an error  
when

  generating the page and it was left out of the distribution [1].

 C'mon.  Anakia's documentation is anything but hard to find.   
I'm all
 for getting things right, but not for holding back releases  
based on

 one missing doc.  I'd rather you let Henning release 1.5 now and
 release 1.5.1 yourself next week.

  I'm concerned about two things.  I'm concerned about a  
prominent bad
  link on the main menu, and I'm concerned the last minute vote  
on the
  final release might not have uncovered additional problems.   
We've a

  chance to make a major impression on the Java world with this
  prominent release and I want this to be very smooth  
installation for
  both new users and the typical existing user who wants to  
upgrade.


 We can't cower in fear of unknown bugs.  Fix what you know and care
 about, then let's get this thing moving again.

  My recommendation is to delay the release until there's time  
to fix
  these doc issues and for more thorough testing.  Mid-March  
seems fine.
   For the shallow bugs theory to work, we need to issue a  
release
  candidate that everyone can work with.  This doesn't need to  
be an
  actual release, just a binary distribution we can test.  After  
a few

  weeks we should be assured the details are 100% set.

 How about two betas and a test build?  That's what we've had.  This
 release has had much time to prepare.  More time won't kill us, but
 let's not pretend things are ever likely to be 100% set.  Trust  
me, if

 i cared enough, i could start combing thru the docs of almost any
 major project you like and find dozens of errors.  Same goes for  
most
 code.   Final releases will never be perfect, but the shallow  
bugs
 theory won't work if we don't get *them* out there.  Far fewer  
people

 bother with release candidates and betas.

  Incidentally, I disagree with Henning's comment that the beta2  
had no
  errors.  Actually, beta2 had a serious error in the build  
process in
  which ant test failed when run from the actual  
distribution.  It
  worked from the source distribution but not the released  
package.  No

  one found this problem for a month.

 And it's fixed, is it not?

  I can't adequately express my admiration of Henning's efforts  
in the

  last 6 months to get this out. This must be frustrating.  I take
  responsibility myself for not thinking through the  
implications of the

Re: svn commit: r500648 - /velocity/engine/branches/Velocity_1.5_BRANCH/

2007-01-29 Thread Geir Magnusson Jr.



On Jan 29, 2007, at 8:09 PM, Nathan Bubna wrote:


I believe the 1.6 was a typo.  He was just suggesting that

velocity/engine/branches/Velocity_1.5_BRANCH

might be simply renamed

velocity/engine/branches/1.5

so that velocity and branch aren't repeated in the path.  :)


yep - thanks for clarifying.  The 1.6 was a typo.

geir



On 1/29/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote:

Geir Magnusson Jr. [EMAIL PROTECTED] writes:

Isn't that redundant Velocity_1.6_BRANCH?

it's in the velocity project, in the branches directory...  how  
about

1.5?

[...]

 Added:
 velocity/engine/branches/Velocity_1.5_BRANCH/
   - copied from r500647, velocity/engine/trunk/

? Sorry I don't understand this mail. Please elaborate.

Best regards
Henning



--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

-
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]




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

Re: Automatic Site rebuild

2007-01-29 Thread Geir Magnusson Jr.


can't other people build the docs?


On Jan 29, 2007, at 10:24 PM, Henning Schmiedehausen wrote:


Hi,

quick idea: As we will not get the zone on time and I will leave at
least my mail server running and connected to the internet, I could  
set

up a once daily / twice daily build on that machine. Downside to it
is, that if I get lost in the Outback and it runs amok, you might  
not be

able to stop it (short of closing my people.apache.org account...
=:-) )

That would be a temporary solution and there would be no further  
excuse

not to work on the docs. :-)

Best regards
Henning

--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.



-
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]

Re: [VOTE]: Release Velocity 1.5

2007-01-27 Thread Geir Magnusson Jr.

Normally yes - you vote on the final software that's going to be  
released, not just the concept.


At the moment, I have no clue what would actually go out the door wrt  
the binary (included libs, LICENSE and NOTICE files, etc)


Should be easy.

geir

On Jan 27, 2007, at 6:20 AM, Henning P. Schmiedehausen wrote:


Geir Magnusson Jr. [EMAIL PROTECTED] writes:


I assume we'll have another vote on the final binary?



geir


Do we need to? The code itself will not change, just some doc file,
change logs etc.

Best regards
Henning





On Jan 27, 2007, at 3:52 AM, Henning P. Schmiedehausen wrote:



Will Glass-Husain [EMAIL PROTECTED] writes:

Hi,

I'd say that I fully agree with your points. This is part of the  
docs

cleanup before we release the code.

Best regards
Henning



Hi Henning,



+1, with a caveat...



Users will want to see specifics of what's new with the system.
Where's the change list?  Will Maven generate this  
automatically?  I

suggest we have two items



* a copy of the release notes from the Wiki, moved into the main
distro as RELEASE-NOTES.txt.  This summarizes key changes and  
more

importantly, dependency changes.



* a maven generated list from changes.xml



I'm +1 if we have those two things.


As an aside, It's incredible all the work you've done,  
especially in

the past few months.



WILL



On 1/24/07, Malcolm Edgar [EMAIL PROTECTED] wrote:

Been waiting for this day for a while now :)

+1

On 1/25/07, Nathan Bubna [EMAIL PROTECTED] wrote:

+1

On 1/24/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:

Let's do it.

The list of changes
(http://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12310253styleName=TextprojectId=12310104Create=Create 
)

is much longer than it ought to be, the number of open issues
is more or less down to zero and no new issues have been
reported with beta 2. I think, it is time now.

Stuff that I do expect to change between now (CfV) and
then (Relase)
are all non code:

- Further work on the docs
- A Maven 2 POM so that the Mavenatics don't need to pull
velocity.jar
and velocity-dep.jar in all the time
- Updates on the xdocs themselves.


[ ] +1 Let's do it
[ ]  0 I don't care
[ ] -1 No, because __

The vote will go for ~72 hours, that is Saturday, 27th, 18:00  
MET

(http://www.timeanddate.com/worldclock/fixedtime.html?
month=1day=27year=2007hour=18min=0sec=0p1=37)

My vote is +1

Best regards
Henning



 
--

---
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]




-- 
--

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






--
Forio Business Simulations



Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com


--- 
--

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


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

 
-

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]


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

-
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]

Re: [VOTE]: Release Velocity 1.5

2007-01-27 Thread Geir Magnusson Jr.



On Jan 27, 2007, at 10:36 AM, Rahul Akolkar wrote:


On 1/27/07, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:

Normally yes - you vote on the final software that's going to be
released, not just the concept.


snip/

Indeed. I'd also like to see velocity votes (as am catching up on ML
reading, noticed a couple following this pattern) point to the actual
artifacts being proposed for release.


That would be what I was talking about, yes :)

geir



-Rahul



At the moment, I have no clue what would actually go out the door wrt
the binary (included libs, LICENSE and NOTICE files, etc)

Should be easy.

geir


snap/

-
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]

Re: [VOTE]: Release Velocity 1.5

2007-01-27 Thread Geir Magnusson Jr.



On Jan 27, 2007, at 2:01 PM, Henning P. Schmiedehausen wrote:


Geir Magnusson Jr. [EMAIL PROTECTED] writes:


Normally yes - you vote on the final software that's going to be
released, not just the concept.



At the moment, I have no clue what would actually go out the door wrt
the binary (included libs, LICENSE and NOTICE files, etc)



Should be easy.


Hm. That *is* a strong imbalance IMHO between projects that ship docs
as part of their distribution (like we do) and others that simply keep
and update their docs online and ship just e.g. javadocs.


It's not just about docs - it's about the whole thing.  How else can  
we say we did proper oversight for things such as the license,  
copyrights, notices and included 3rd party dependencies when we can't  
see it?




In that case, I'd actually like to discuss removing all docs except
automatically created docs from source (e.g. Javadocs, Changelog etc.)
from the distribution archives.


Why?  Aren't our docs checked in too somewhere, or can be  
mechanically re-created from checked-in sources?




We do have to discuss the actual release process. Other projects
(e.g. httpd) do it differently, they roll their distribution archives
first and then vote on them. We do it the other way around.


So here's my suggestion - choose some process that in the end  
produces a build that a) can be re-created by anyone based on knowing  
the svn revision and b) outputs the binary packaging that we can vote  
on to be our released artifacts.


geir




Best regards
Henning





geir



On Jan 27, 2007, at 6:20 AM, Henning P. Schmiedehausen wrote:



Geir Magnusson Jr. [EMAIL PROTECTED] writes:


I assume we'll have another vote on the final binary?



geir


Do we need to? The code itself will not change, just some doc file,
change logs etc.

Best regards
Henning





On Jan 27, 2007, at 3:52 AM, Henning P. Schmiedehausen wrote:



Will Glass-Husain [EMAIL PROTECTED] writes:

Hi,

I'd say that I fully agree with your points. This is part of the
docs
cleanup before we release the code.

Best regards
Henning



Hi Henning,



+1, with a caveat...



Users will want to see specifics of what's new with the system.
Where's the change list?  Will Maven generate this
automatically?  I
suggest we have two items



* a copy of the release notes from the Wiki, moved into the main
distro as RELEASE-NOTES.txt.  This summarizes key changes and
more
importantly, dependency changes.



* a maven generated list from changes.xml



I'm +1 if we have those two things.



As an aside, It's incredible all the work you've done,
especially in
the past few months.



WILL



On 1/24/07, Malcolm Edgar [EMAIL PROTECTED] wrote:

Been waiting for this day for a while now :)

+1

On 1/25/07, Nathan Bubna [EMAIL PROTECTED] wrote:

+1

On 1/24/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:

Let's do it.

The list of changes
(http://issues.apache.org/jira/secure/ReleaseNote.jspa?
version=12310253styleName=TextprojectId=12310104Create=Crea 
te

)
is much longer than it ought to be, the number of open issues
is more or less down to zero and no new issues have been
reported with beta 2. I think, it is time now.

Stuff that I do expect to change between now (CfV) and
then (Relase)
are all non code:

- Further work on the docs
- A Maven 2 POM so that the Mavenatics don't need to pull
velocity.jar
and velocity-dep.jar in all the time
- Updates on the xdocs themselves.


[ ] +1 Let's do it
[ ]  0 I don't care
[ ] -1 No, because __

The vote will go for ~72 hours, that is Saturday, 27th, 18:00
MET
(http://www.timeanddate.com/worldclock/fixedtime.html?
month=1day=27year=2007hour=18min=0sec=0p1=37)

My vote is +1

Best regards
Henning



-- 
--

--
---
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]




 
--

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






--
Forio Business Simulations



Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com


- 
--

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


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity -  
Turbine guy


  Save the cheerleader. Save the world.

-- 
--

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

Re: [VOTE]: Release Velocity 1.5

2007-01-27 Thread Geir Magnusson Jr.



On Jan 27, 2007, at 3:26 PM, Will Glass-Husain wrote:


To me there seems a qualitative difference between a beta and a rc or
final release.


There isn't from the POV of oversight.



Keeping it less formal for a beta release seems fine.  But for a
release candidate Geir's points make sense.  Either we should be
voting on a specific binary, or the on the result of typing ant
package with the current svn source.


Vote on the binary.  That way we call can smoke test it to make sure  
it's right.




Also, we definitely need to distribute full docs.

WILL

On 1/27/07, Nathan Bubna [EMAIL PROTECTED] wrote:

On 1/27/07, Henning P. Schmiedehausen [EMAIL PROTECTED] wrote:
 Geir Magnusson Jr. [EMAIL PROTECTED] writes:

 Normally yes - you vote on the final software that's going to be
 released, not just the concept.

 At the moment, I have no clue what would actually go out the  
door wrt

 the binary (included libs, LICENSE and NOTICE files, etc)

 Should be easy.

 Hm. That *is* a strong imbalance IMHO between projects that ship  
docs
 as part of their distribution (like we do) and others that  
simply keep

 and update their docs online and ship just e.g. javadocs.

 In that case, I'd actually like to discuss removing all docs except
 automatically created docs from source (e.g. Javadocs, Changelog  
etc.)

 from the distribution archives.

-1  i like keeping docs with distros, both source and binary.  and as
Geir said, it doesn't really solve the problem.

 We do have to discuss the actual release process. Other projects
 (e.g. httpd) do it differently, they roll their distribution  
archives

 first and then vote on them. We do it the other way around.

+1 !!  i've been thinking about this for quite some time.  i like the
freedom httpd-ish projects have to change the status of a release (in
any direction) without having to re-roll it.  at the latest, i'd like
to see us adopt this after Engine 1.5 and Tools 1.3 are out.  it's a
little superfluous to switch to this now since we've already been
stepping through betas and RCS, but if people really wanted to start
now, that's fine by me. :)

 Best regards
 Henning




 geir

 On Jan 27, 2007, at 6:20 AM, Henning P. Schmiedehausen wrote:

  Geir Magnusson Jr. [EMAIL PROTECTED] writes:
 
  I assume we'll have another vote on the final binary?
 
  geir
 
  Do we need to? The code itself will not change, just some doc  
file,

  change logs etc.
 
   Best regards
   Henning
 
 
 
 
  On Jan 27, 2007, at 3:52 AM, Henning P. Schmiedehausen wrote:
 
  Will Glass-Husain [EMAIL PROTECTED] writes:
 
  Hi,
 
  I'd say that I fully agree with your points. This is part  
of the

  docs
  cleanup before we release the code.
 
 Best regards
 Henning
 
 
  Hi Henning,
 
  +1, with a caveat...
 
  Users will want to see specifics of what's new with the  
system.

  Where's the change list?  Will Maven generate this
  automatically?  I
  suggest we have two items
 
  * a copy of the release notes from the Wiki, moved into  
the main
  distro as RELEASE-NOTES.txt.  This summarizes key  
changes and

  more
  importantly, dependency changes.
 
  * a maven generated list from changes.xml
 
  I'm +1 if we have those two things.
 
  As an aside, It's incredible all the work you've done,
  especially in
  the past few months.
 
  WILL
 
  On 1/24/07, Malcolm Edgar [EMAIL PROTECTED] wrote:
  Been waiting for this day for a while now :)
 
  +1
 
  On 1/25/07, Nathan Bubna [EMAIL PROTECTED] wrote:
  +1
 
  On 1/24/07, Henning Schmiedehausen [EMAIL PROTECTED]  
wrote:

  Let's do it.
 
  The list of changes
  (http://issues.apache.org/jira/secure/ReleaseNote.jspa?
   
version=12310253styleName=TextprojectId=12310104Create=Create

  )
  is much longer than it ought to be, the number of open  
issues

  is more or less down to zero and no new issues have been
  reported with beta 2. I think, it is time now.
 
  Stuff that I do expect to change between now (CfV) and
  then (Relase)
  are all non code:
 
  - Further work on the docs
  - A Maven 2 POM so that the Mavenatics don't need to pull
  velocity.jar
  and velocity-dep.jar in all the time
  - Updates on the xdocs themselves.
 
 
  [ ] +1 Let's do it
  [ ]  0 I don't care
  [ ] -1 No, because __
 
  The vote will go for ~72 hours, that is Saturday, 27th,  
18:00

  MET
  (http://www.timeanddate.com/worldclock/fixedtime.html?
  month=1day=27year=2007hour=18min=0sec=0p1=37)
 
  My vote is +1
 
  Best regards
  Henning
 
 
 
   


  --
  ---
  To unsubscribe, e-mail: dev- 
[EMAIL PROTECTED]
  For additional commands, e-mail: dev- 
[EMAIL PROTECTED]

 
 
 
   
-

  --
  --
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: dev- 
[EMAIL PROTECTED

Re: svn commit: r500648 - /velocity/engine/branches/Velocity_1.5_BRANCH/

2007-01-27 Thread Geir Magnusson Jr.


Isn't that redundant Velocity_1.6_BRANCH?

it's in the velocity project, in the branches directory...  how about  
1.5?


geir

On Jan 27, 2007, at 5:39 PM, [EMAIL PROTECTED] wrote:


Author: henning
Date: Sat Jan 27 14:39:05 2007
New Revision: 500648

URL: http://svn.apache.org/viewvc?view=revrev=500648
Log:
Creating a release branch

Added:
velocity/engine/branches/Velocity_1.5_BRANCH/
  - copied from r500647, velocity/engine/trunk/




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

Re: Get ready for CfV

2007-01-23 Thread Geir Magnusson Jr.


What are the high points to be mentioned?

On Jan 23, 2007, at 2:49 PM, Henning P. Schmiedehausen wrote:


Geir Magnusson Jr. [EMAIL PROTECTED] writes:

Let's see... ...the first release of one of the most popular
templating engines in the java world since more than two years...

I'd say yes. We did bigger PR for less visible projects. :-)

Best regards
Henning




Do you think this is really worthy of a press release?



On Jan 23, 2007, at 4:49 AM, Henning P. Schmiedehausen wrote:



So folks, I think it is about time now to bite the bullet, call it a
day and get Velocity 1.5 out.

Unless anyone objects, I will CfV to release the current HEAD as
Velocity 1.5 tomorrow, 12 PM (noon). All still open issues get moved
to 1.6 by the time of the CfV.

Will: Can you ramp up the PRC connection to get a press release  
by the

end of next week?

Best regards
Henning


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

 
-

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]


--
Henning P. Schmiedehausen  -- [EMAIL PROTECTED] | J2EE, Linux,
91054 Buckenhof, Germany   -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy

  Save the cheerleader. Save the world.

-
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]

Re: is Texen orphaned?

2006-11-25 Thread Geir Magnusson Jr.




Will Glass-Husain wrote:

Hi,

Apparently, the main example in the Texen docs in Velocity 1.4 is
broken.  Geir broke it in early 2002, and Shinobu found and fixed the
problem in early 2005.  So while this has been fixed for 1.5, for the
past couple of years the docs for the released version 1.4 have been
wrong and no one has complained.



How did I break it?


http://issues.apache.org/bugzilla/show_bug.cgi?id=5183
http://issues.apache.org/bugzilla/show_bug.cgi?id=33206
http://jakarta.apache.org/velocity/docs/texen.html

Also, there don't seem to be any experienced users on the mailing
list.  When a user recently asked about this no one responded until I
had a chance to look into it.  (I try to be responder-of-last-resort
for these type of things).

My point... Texen seems like an orphaned project.  I'm guessing
there's a few embedded users (Torque) so we shouldn't drop it.  But
I'd like to move it (after 1.5) to a separate subproject.  Probably
Anakia too.  Comments?


+1



WILL



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

Re: ApacheCon NA 2017

Re: Velocity Macro Stack Traces Patch

Re: [VOTE] Release Velocity Engine 1.6

Re: [VOTE] Release VelocityTools 2.0-beta3

Re: [VOTE] Release VelocityTools 2.0-beta3

Re: [VOTE] Release VelocityTools 2.0-beta3

Re: [VOTE] Release VelocityTools 2.0-beta3

Re: [VOTE] Release VelocityTools 2.0-beta3

Re: What is schmoo

Re: Call a velocity macro

Re: Call a velocity macro

Re: Call a velocity macro

Re: Call a velocity macro

Re: svn commit: r579331 - in /velocity/engine/trunk/src: java/org/apache/velocity/util/introspection/UberspectImpl.java test/org/apache/velocity/test/ForeachTestCase.java

Re: DVSL

Re: [Fwd: Incubation of the Click Project at the Apache Software Foundation]

Re: update on site issues

Re: update on site issues

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )

Re: svn commit: r500648 - /velocity/engine/branches/Velocity_1.5_BRANCH/

Re: Automatic Site rebuild

Re: [VOTE]: Release Velocity 1.5

Re: [VOTE]: Release Velocity 1.5

Re: [VOTE]: Release Velocity 1.5

Re: [VOTE]: Release Velocity 1.5

Re: svn commit: r500648 - /velocity/engine/branches/Velocity_1.5_BRANCH/

Re: Get ready for CfV

Re: is Texen orphaned?

31 matches

Site Navigation

Mail list logo

Footer information