Re: git migration
On 4/5/19 6:54 AM, Claude Brisson wrote: What about moving to git? +1 from me - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org Yes please +1 - 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
+1 from me. 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] -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar RADRACE 2006,2007 en 2008: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Velocity Engine 1.6-beta1 test build 2
+1 works fine. Nathan Bubna wrote: There was no negative feedback on the 2nd test build (no feedback at all actually), so i'm moving on to a vote again. The test build is still available here: http://people.apache.org/~nbubna/velocity/engine/1.6-beta1/ Please vote regarding your support for releasing this new test build as Velocity Engine 1.6-beta1: [ ] +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 9am PST on Friday, Sep 19th. If the vote passes, I'll push this to the mirrors and perhaps begin struggling to update the web site that afternoon. Of course, recent history indicates that there's really no telling when i'll actually succeed with that last part and be able to announce the release. On Wed, Sep 10, 2008 at 11:15 AM, Nathan Bubna [EMAIL PROTECTED] wrote: The last test build for 1.6-beta1 failed due to some missing license headers. It's been replaced by a new build for Engine 1.6-beta, this one based on revision 693911. http://people.apache.org/~nbubna/velocity/engine/1.6-beta1/ please kick the tires and report any other nitpicks soon. you don't have to wait for the CfV to form an opinion on this. :) anyway, assuming no one sees any problems, i'll call for another release vote on Friday or Saturday, aiming for a release on Monday or Tuesday. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar RADRACE 2006,2007 en 2008: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Velocity Engine 1.6-beta1
+1 from me. Nathan Bubna wrote: There was no negative feedback on the test build (no feedback at all actually), so i'm moving on to a vote... The test build is still available here: http://people.apache.org/~nbubna/velocity/engine/1.6-beta1/ Please vote regarding your support for releasing this test build as Velocity Engine 1.6-beta1: [ ] +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 10am PST on Thursday, Jul 3rd. If the vote passes, I'll push this to the mirrors and begin struggling to update the web site that afternoon. Of course, recent history indicates that there's really no telling when i'll actually succeed with that last part and be able to announce the release. On Tue, Sep 2, 2008 at 9:07 PM, Nathan Bubna [EMAIL PROTECTED] wrote: ok folks, here's a build for Engine 1.6-beta. http://people.apache.org/~nbubna/velocity/engine/1.6-beta1/ please kick the tires and report any nitpicks soon. assuming no one sees any problems, i'll call for a release vote in a few days. with luck, that vote will close early next week, and i can push this release out. thanks, nathan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar RADRACE 2006,2007 en 2008: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Call a velocity macro #stop
Please stop this. Daniel Dekany wrote: Monday, March 10, 2008, 1:21:59 PM, Geir Magnusson Jr. wrote: Steven, Don't judge this community by this thread - we have a long history of constructive and positive collaborative development. Right... with results like Velocity. It speaks for itself. (And may I notice, what a typical corporal bullshit you are saying.) Give it another chance. geir -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar Development Tools 2006 en 2007: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Call a velocity macro #stop
PLS STOP THIS
Jonathan Revusky wrote:
Konstantin Priblouda wrote:
--- Adrian Tarau [EMAIL PROTECTED] wrote:
I agree, don't judge any online community based on
guys like Jonathan. Just ignore them...
funny thig is, it' s spillover from completely
different community ;)
What different community? What are you talking about? The origin of
this thread is Adrian responding to my private note on a public list,
this one. The poor boy thought it was so shocking that I said that
Velocity (and I was quite specific referring to its macro system) as
junk in a private note, it was so shocking that he just had to reply
to me in a lecturing tone *in public*!!!
And then this guy continually lies subsequently, that he had heatedly
written a response to me automatically. If he'd done that, he would
have hit reply-to and would have answered in private. He then later
referred to my private email as a rant, he had never seen anything
like that in 8 years! THat was really a lie, I mean, what I wrote him
in private a technically focused note. I'm going to provide it again
so you see what kind of snivelling lying scum this guy is.
The text of my rant (according to Adrian) follows:
--
Adrian Tarau wrote:
I've always used #if to implement the 'switch' but I think, even for
3-4
conditions, the template will look cleaner.
Instead of
#if('renderLabel' == $macroToCall)
#renderLabel($component)
#elseif('renderInput' == $macroToCall)
#renderInput($component)
#elseif(...)
...
#end
we will have
#call($macroToCall $component).
This kind of thing is trivial in FreeMarker. For example, suppose you
had:
#assign macroHash = {'renderLabel' : labelMacro, 'renderInput' :
renderMacro,
and then, supposing you have an action string, like suppose:
[#assign action = 'renderLabel']
then you could invoke the macro via:
@macroHash[action] component /
The thing is that macros in FreeMarker are variables, and can be in
hashes or assigned to variables or whatever, and also the foo in
@foo/ to invoke the macro can be any arbitrary expression.
So, for example, suppose the macro you want to invoke is in the string
macroName, you could invoke it via:
@.vars[macroName] component/
(.vars is a special built-in hash that contains the variables
available in the template and since macros are variables as well,
.vars[macroName] is the macro with the name macroName and it can be
invoked this way, or you could create a variable.
#assign myMacro = .vars[macroName]
and invoke it via:
@myMacro component/
Well, in general, once you want to do anything moderately complex with
velocimacros, the thing breaks because it's junk. :-)
Here is a blog entry I wrote regarding some of this sort of thing:
http://freemarker.blogspot.com/2007/12/velocity-of-freemarker-looking-at-5.html
[ Konstantin Pribluda http://www.pribluda.de ]
JTec quality components: http://www.pribluda.de/projects/
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.
Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Matthijs Lambooy
CrossmarX BV, Amsterdam
http://www.crossmarx.com
+31654771926
skype callto://matthijslambooy
xmpp:[EMAIL PROTECTED]
Winnaar Development Tools 2006 en 2007: http://www.crossmarx.com/radrace
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Call a velocity macro
Well Jonathan gives me another good reason to use velocity Thanks Jonathan!! Jonathan Revusky wrote: Gonzalo Diethelm wrote: On Sun, 2008-03-09 at 18:21 +0100, Jonathan Revusky wrote: Adrian, you little dipshit, ... To the moderator of this forum: doesn't this language constitute grounds for banning this person from these lists? You seriously are proposing banning somebody (me in this instance) for calling somebody a dipshit? (Especially after the dipshit in question posted a private message to a public forum to try to embarrass that person?) And to make matters worse, the little dipshit told at least a couple of transparent lies afterwards to try to justify himself, like the bit about how I wrote some incredible rant to him in private that was so shocking, he'd never seen anything like this in 8 years... there's no generous interpretation of that, he was just lying So... schematically: a guy breaches nettiquette by posting a private message in public and subsequently tells lies about the incident, and you're going to ban not that individual, but the person at the receiving end who tells him off. Anyway, nobody would believe that your grounds for banning me (calling the dipshit a dipshit) were the real grounds. They'd see me pointing out quite truthfully the state of this project and know perfectly well that that was the reason for the banning. Jonathan Revusky -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar Development Tools 2006 en 2007: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Call a velocity macro
:-D Jonathan Revusky wrote: Matthijs Lambooy wrote: Well Jonathan gives me another good reason to use velocity How is that a reason to use Velocity? I know you're trying to tell me off (and suck up to the people you feel are the relevant authority figures) but it's unsettling that there isn't even the slightest attempt at logical (or pseudological) discourse. Summary: A dipshit writes a response to my private message in public and I tell him off and another self-righteous ass says I should be banned for telling him off. And that's a good reason for you to use Velocity. I mean, there's no logical connection anywhere. It's like: The socialists were just reelected in Spain. That's a good reason to use Velocity. Damn right. Why don't you just say Yer mommy wears army boots! or something. At least it's something of an insult (at the primary school level anyway...) Or really, try to make some technical argument in defense of how great Velocity supposedly is, we could talk about that... Thanks Jonathan!! You're welcome, I guess shrug Oh, here are a couple more good reasons for people to use Velocity. The price of crude oil is at a record high. Pamela Anderson still has big tits. Jonathan Revusky -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] Winnaar Development Tools 2006 en 2007: http://www.crossmarx.com/radrace - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing it
Hi All. Congratulations! Matthijs Lambooy Henning Schmiedehausen wrote: Hi, thanks for doing this! It seems that this process is still a bit rough and it is one of my top priorities to get this smoother and that we can run it from the zone. I've did a minor update on the main page, there was still 1.4 as release and 1.5 beta 2 as beta listed. I noticed that for the site, the pages that go through the velocity/doxia renderer did not get updated (they still had 1.4 as release), so I assume that this is one of the rough edges. Will look into this. Also for the Engine site, the JIRA report listed only a few issues, this might be a problem with the jira report plugin (I've contributed lots of fixes here). I've deployed both sites again, they should be fine now. Best regards Henning On Tue, 2007-03-06 at 17:27 -0800, Nathan Bubna wrote: On 3/6/07, Nathan Bubna [EMAIL PROTECTED] wrote: On 3/6/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: On Tue, 2007-03-06 at 10:09 -0800, Nathan Bubna wrote: If you'd prefer, i'd be happy to cede the update of the web site to you or at least enlist your help. I've got things working adequately, but not splendidly. Things left to be done for the 1.5 release are: As you wish. I can build it if you want me to. With the zone now finally being available I'm currently setting up ant, maven and all that stuff so we can build from a common environment. that'd be good. if you haven't noticed, i've had to disable the news macro and roughly mimic it's results by hand. if you can make it work properly, i think that would be preferable. of course, i do want us to figure out how to make it work fully for others besides you, but we can do that later. ok, i deployed the site using the site module as it is in svn (with the news macro disabled and hand-mimicked). you're of course still quite welcome to re-update with the news macro working, and to fix and bad in-page anchors or whatever. so, the public now has access to Velocity 1.5 from our download page, if they happen to visit the web site before the announcements go out by email. - use mvn to deploy the changes i just checked in this morning. i'm waiting until a few more mirrors pick up the build before i do that. Sure. These are changes to the Velocity Site, right? yep. updated the download page, the doap descriptor, the front page and the menu sidebar thing. - update the Engine 1.5 subsection. i'm not entirely sure how you do this. currently, there is an older version (from one of your attempted releases in January, i presume) up at http://velocity.apache.org/engine/releases/velocity-1.5/, but this doesn't reflect any changes since then (e.g. the change log doesn't show the fix for SecureUberspector). i'm not sure yet what the procedure for doing this is. In the engine release, run mvn clean post-site site:deploy. That should push the release version of the site up. This should overwrite all the files you mentioned. let me give this part a try. i haven't done this yet and would like to see it work for me. it appears to have worked just fine... - create the release tag. That why I asked about the revision. I did svn -m Velocity 1.5 Release copy -r 509925 \ https://svn.apache.org/repos/asf/velocity/engine/branches/Velocity_1.5_BRANCH \ https://svn.apache.org/repos/asf/velocity/engine/tags/Velocity_1.5 yeah, i saw that. thanks. for that. I MD5 checked the files from the branch and the tag and they all checked out ok, even though the files on the tag technically have another revision number. that's to be expected. revision numbers are only updated in files which are changed and which have the $Id$ thingy in 'em. - Deploy the release to the maven repo. another thing i've never done. i presume there's a magic maven command for this too? i think this last item and the email announcements are all that's left to be done. Will said he'd handle the PR. Anyone who wants to deploy 1.5 to the maven repo or tell me how to do it is welcome to do so. Best regards Henning -- Henning P. Schmiedehausen -- [EMAIL PROTECTED] | J2EE, Linux, |gls 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau Open Source Consulting, Development, Design| Velocity - Turbine guy |rwc |m k INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] http://www.zoook.nl laat zien wat je te koop hebt
Re: [VOTE] Release Velocity 1.5 (again, this time for real. :-) )
+1 Matthijs Lambooy Malcolm Edgar wrote: +1 regards Malcolm Edgar On 1/29/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: Due to a misunderstanding in the vote procedure, we actually have to repeat the release vote, because we should vote only on really rolled releases. The candidate for the Apache Velocity 1.5 release is available from http://people.apache.org/dist/velocity/1.5/ Shall we release this code base as Apache Velocity 1.5 [ ] +1 Yes. [ ] 0 I still don't care. [ ] -1 No, because . Vote period is Monday, Jan 29th 0:00 MET to Wednesday, Jan 31st 0:00 MET 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] -- Matthijs Lambooy CrossmarX BV, Amsterdam http://www.crossmarx.com +31654771926 skype callto://matthijslambooy xmpp:[EMAIL PROTECTED] http://www.zoook.nl laat zien wat je te koop hebt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
