[jira] [Commented] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394974#comment-17394974 ] Mike Kienenberger commented on VELOCITY-947: I'll still do fixes against 1.7.x if someone

[jira] [Commented] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394803#comment-17394803 ] Mike Kienenberger commented on VELOCITY-947: I don't think many people are using the 1.7.x

[jira] [Reopened] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-947: Apparently not a configuration issue.  Re-opening. > Input macro varia

[jira] [Comment Edited] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394787#comment-17394787 ] Mike Kienenberger edited comment on VELOCITY-947 at 8/6/21, 2:00 PM

[jira] [Resolved] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-947. Resolution: Not A Bug I'm pretty sure this is a matter of setting configuration

[jira] [Commented] (VELOCITY-947) Input macro variable not changed outside scope

[ https://issues.apache.org/jira/browse/VELOCITY-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394782#comment-17394782 ] Mike Kienenberger commented on VELOCITY-947: Everything you've said is likely true

Re: [OT] Problems with commons-beanutils-1.9.4

I'm still maintaining a project using a Velocity 1.8-snapshot and struts. If I recall, I think the lack of a path forward for struts was why I did not upgrade to 2.x. But I'm also stuck with an ancient version of struts, so my situation may be unique. On Sat, Mar 14, 2020 at 9:47 AM Christopher

[jira] [Commented] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6 for Velocity 1.x.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979364#comment-16979364 ] Mike Kienenberger commented on VELOCITY-816: Sorry – It's been so long that I can't

[jira] [Closed] (VELOCITY-899) Update build process for Java 1.8 and new dependency locations

[ https://issues.apache.org/jira/browse/VELOCITY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELOCITY-899. -- Resolution: Fixed Fix Version/s: 1.7.x Fixed on 1.7.x branch. > Update bu

[jira] [Closed] (VELOCITY-882) Critical vulnerability in commons collection

[ https://issues.apache.org/jira/browse/VELOCITY-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELOCITY-882. -- Resolution: Fixed Fixed on 1.7.x branch. > Critical vulnerability in comm

[jira] [Updated] (VELOCITY-882) Critical vulnerability in commons collection

[ https://issues.apache.org/jira/browse/VELOCITY-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-882: --- Fix Version/s: 2.0 1.7.x > Critical vulnerability in comm

[jira] [Reopened] (VELOCITY-882) Critical vulnerability in commons collection

[ https://issues.apache.org/jira/browse/VELOCITY-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-882: Assignee: Mike Kienenberger It's a simple fix for branch 1.7.x so I'll go

[jira] [Updated] (VELOCITY-899) Update build process for Java 1.8 and new dependency locations

[ https://issues.apache.org/jira/browse/VELOCITY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-899: --- Description: - Update Velocity version to 1.7.1. - Update required java version

[jira] [Updated] (VELOCITY-899) Update build process for Java 1.8 and new dependency locations

[ https://issues.apache.org/jira/browse/VELOCITY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-899: --- Description: - Dependency location in maven has changed again

[jira] [Updated] (VELOCITY-899) Update build process for Java 1.8 and new dependency locations

[ https://issues.apache.org/jira/browse/VELOCITY-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-899: --- Description: Dependency location in maven has changed again.   > Update bu

[jira] [Created] (VELOCITY-899) Update build process for Java 1.8 and new dependency locations

Mike Kienenberger created VELOCITY-899: -- Summary: Update build process for Java 1.8 and new dependency locations Key: VELOCITY-899 URL: https://issues.apache.org/jira/browse/VELOCITY-899 Project

Re: Problem in Eclipse with JBoss's java2ws using velocity - "The specified logger class org.apache.velocity.runtime.log.NullLogSystem does not implement the org.apache.velocity.runtime.log.LogChute i

While I can't share the code, one of my clients has written a generic class that dumps the current app's classpath, so this can be done within your own java code. The code I have access to is much more complicated, but a simple approach can be found here:

Velocity 2 press release announcement

It might be worthwhile to send a message to press@ to start the process of creating a velocity 2 press release. MyFaces Tobago is working through that process now, and while I am not directly involved, it appears that Sally will prepare a draft press release for you and someone from velocity

Re: [tools] Tools reeng

On Thu, Nov 17, 2016 at 12:58 PM, Claude Brisson wrote: > There are several things I'd like to do for the tools before releasing them: > > 1) deprecate the ConversionTool: > - the only remaining feature is a toStrings() method (which does > splitting and optional

Re: Logging configuration

+1 to using several appropriate functional names if we are picking loggers by String rather than by Class. On Thu, Nov 10, 2016 at 11:11 AM, Claude Brisson wrote: > On 10/11/2016 15:56, Greg Huber wrote: > >> Yes it does when I use name="Velocity" >> >> But as you are using

Re: [tools] status of the velocity-tools-struts module?

I maintain a project that uses struts tools, but my version of struts tools (like my version of velocity and struts) is so old that maintaining the "current" struts tools version isn't useful to me. I maintained my own version of my tools on those rare occasions where it was necessary. If no

Re: [VOTE] Release velocity-master 2

Don't revert on my behalf. It doesn't matter to me if I'm listed as a committer in the pom, and it can always be corrected in a future release. But did you ever publish the staging URL? I don't remember seeing it. On Fri, Oct 14, 2016 at 8:56 AM, Claude Brisson wrote: > I

Re: [VOTE] Release velocity-master 2

I took a look at the MyFaces release page, which in turn points to the following url. Starting at this section, it does look like you now have all of the pieces you need in place: prepare the release, perform the release, close the respository, take the vote.

Re: [VOTE] Release velocity-master 2

On Tue, Oct 11, 2016 at 8:11 AM, Claude Brisson wrote: > (I don't know where snapshots and prepared releases do land on > https://repository.apache.org , I was unable to find them on > https://repository.apache.org after the release:prepare call, which > apparently went

Re: svn commit: r1758416 [1/3] - in /velocity/engine/trunk/velocity-engine-core/src: main/java/org/apache/velocity/runtime/ main/java/org/apache/velocity/runtime/parser/node/ main/java/org/apache/velo

What? You would dare to impose your view of configurable whitespace gobbling upon the rest of us after only a mere decade of discussion? What will we talk about for the next 10 years? :-) On Tue, Aug 30, 2016 at 12:18 PM, wrote: > Author: cbrisson > Date: Tue Aug 30

[jira] [Commented] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6 for Velocity 1.x.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15382189#comment-15382189 ] Mike Kienenberger commented on VELOCITY-816: I think a 2.x release is high on Claude's

[jira] [Commented] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6 for Velocity 1.x.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381569#comment-15381569 ] Mike Kienenberger commented on VELOCITY-816: Oops. Thanks for correcting the fix version

[jira] [Updated] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6 for Velocity 1.x.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-816: --- Summary: Upgrade commons-lang from 2.4 to 2.6 for Velocity 1.x. (was: Upgrade

Re: svn commit: r1752882 - in /velocity/engine/trunk/velocity-engine-scripting: ./ src/main/java/org/apache/velocity/script/ src/main/java/org/apache/velocity/script/util/ src/test/java/org/apache/vel

cla...@renegat.net> wrote: > I agree, but does it means we should *remove* the license text? > > I read "Redistributions of source code must retain the above copyright > notice". So I was under the impression that the way to go is to have both > notices in the file. > > >

Re: svn commit: r1752882 - in /velocity/engine/trunk/velocity-engine-scripting: ./ src/main/java/org/apache/velocity/script/ src/main/java/org/apache/velocity/script/util/ src/test/java/org/apache/vel

Signing off that this Sun license falls under A category despite not being explicitly listed. On Fri, Jul 15, 2016 at 6:31 PM, wrote: > Author: cbrisson > Date: Fri Jul 15 22:30:59 2016 > New Revision: 1752882 > > URL: http://svn.apache.org/viewvc?rev=1752882=rev > Log: >

Re: [RESULT] [VOTE] New site layout - Apache CMS

On Thu, May 19, 2016 at 2:38 AM, Perry Tew wrote: > Hey man, it's cool. I figured since I was just a lurker I didn't count. :) > But really, I shouldn't count. I've only taken from this project, never > given, so no apologies. > The site looks stellar, btw. Great job.

Re: [RESULT] [VOTE] New site layout - Apache CMS

I'm still a non-binding vote as well. On Thu, May 19, 2016 at 2:32 AM, Claude Brisson <cla...@renegat.net> wrote: >> switch to this new site and to the Apache CMS? > > The vote was launched more than 48h ago. We already have four +1 binding > votes (Mike Kienenberger, Nat

Re: [VOTE] New site layout - Apache CMS

On Mon, May 16, 2016 at 7:19 PM, Claude Brisson wrote: > Now to the vote: switch to this new site and to the Apache CMS? > > [ ] -1 > [ ] 0 > [ ]+1 +1 from me. I agree that the old site was no longer maintainable. I looked at it at one point but couldn't figure it out.

Re: svn commit: r1696822 - in /velocity/tools/trunk: src/site/xdoc/ velocity-tools-struts/src/main/java/org/apache/velocity/tools/struts/ velocity-tools-view/src/main/java/org/apache/velocity/tools/vi

Chris, Read the whole thread. My understanding is that serialization of static commons-logging was the original problem needing fixed. slf4j doesn't have that issue. On Mon, Aug 31, 2015 at 1:41 PM, Christopher Schultz wrote: > Claude, > > On 8/20/15 3:12 PM,

Go ahead and apply your patches

Bill, You're a committer now, please apply any patches directly to svn that you think are needed. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org

[jira] [Commented] (VELTOOLS-154) Bad tool causes velocity servlet to fail to initialize, chew 100% CPU

[ https://issues.apache.org/jira/browse/VELTOOLS-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702350#comment-14702350 ] Mike Kienenberger commented on VELTOOLS-154: Mohammad, It's unlikely

[jira] [Closed] (VELOCITY-865) I am new velocity .

[ https://issues.apache.org/jira/browse/VELOCITY-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELOCITY-865. -- I am new velocity . Key: VELOCITY-865

[jira] [Resolved] (VELOCITY-865) I am new velocity .

[ https://issues.apache.org/jira/browse/VELOCITY-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-865. Resolution: Not A Problem Please post questions and hold discussions about using

Re: Proposal to add Features to the Apache Velocity Scripting Language

Pick something specific and propose the idea here on the dev@velocity list. If no one objects, we'll have you open a JIRA issue and you can submit your changes as a unified diff patch. Activity has been picking up recently, so you've chosen a good time. On Sat, Jun 27, 2015 at 5:30 AM, Shreyans

[jira] [Commented] (VELTOOLS-166) Syntax error in DOAP file release section

[ https://issues.apache.org/jira/browse/VELTOOLS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582673#comment-14582673 ] Mike Kienenberger commented on VELTOOLS-166: I'll go ahead and fix it since

Need to be added to the VELTOOLS jira admin role

I need to be added to the VELTOOLS jira admin role (mkienenb).I'll probably end up doing work on veltools at some point in any case as it's the other thing I use in addition to engine. - To unsubscribe, e-mail:

[jira] [Assigned] (VELTOOLS-166) Syntax error in DOAP file release section

[ https://issues.apache.org/jira/browse/VELTOOLS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELTOOLS-166: -- Assignee: Mike Kienenberger Syntax error in DOAP file release section

Re: Need to be added to the VELTOOLS jira admin role

, Mike Kienenberger mkien...@gmail.com wrote: I need to be added to the VELTOOLS jira admin role (mkienenb).I'll probably end up doing work on veltools at some point in any case as it's the other thing I use in addition to engine

[jira] [Assigned] (VELOCITY-859) Syntax error in DOAP file release section

[ https://issues.apache.org/jira/browse/VELOCITY-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELOCITY-859: -- Assignee: Mike Kienenberger Syntax error in DOAP file release section

Re: Need to be added to the VELTOOLS jira admin role

. :) On Thu, Jun 11, 2015 at 4:54 PM, Mike Kienenberger mkien...@gmail.com wrote: There's a few more DOAP files I need to fix.I grabbed the issue for VELOCITY. So that just leaves ANAKIA-7 -- can you add me as a jira admin for that project as well? On Thu, Jun 11, 2015 at 7:33 PM, Nathan

[jira] [Closed] (VELTOOLS-166) Syntax error in DOAP file release section

[ https://issues.apache.org/jira/browse/VELTOOLS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELTOOLS-166. -- Resolution: Fixed Added release tags around each set of version tags. Syntax error

[jira] [Closed] (VELOCITY-859) Syntax error in DOAP file release section

[ https://issues.apache.org/jira/browse/VELOCITY-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELOCITY-859. -- Resolution: Fixed Added release tags around each set of version tags. Syntax error

Re: Need to be added to the VELTOOLS jira admin role

admin privs for all Velocity sub-projects now (Anakia, Texen, DVSL, Docbook Framework, etc), assuming i did that right. :) On Thu, Jun 11, 2015 at 5:05 PM, Mike Kienenberger mkien...@gmail.com wrote: It's more of a matter of the global DOAP scripts being messed up due to bad data in our file

Re: general@velocity mailing list

that the general@ mailing list be removed. On Sat, May 30, 2015 at 12:29 PM, Nathan Bubna nbu...@gmail.com wrote: +1 On Sat, May 30, 2015 at 7:58 AM, Frederick N. Brier fnbr...@gmail.com wrote: Sounds good to me :). On 05/30/2015 04:11 AM, Mike Kienenberger wrote: And while we're at it, why

Re: Changing velocity web site

, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site. https://svn.apache.org/repos/asf/velocity/site/site appears

Re: Changing velocity web site

at Committer info section on this page. http://wiki.apache.org/velocity/ WILL On Tue, Jun 9, 2015 at 12:41 PM, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes

Re: Changing velocity web site

On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain wglasshus...@gmail.com wrote: The build process for the site is very old -- is that still applicable after the svnpubsub change? svnpubsub makes it so that whenever you commit to the svnpubsub directory, those changes are immediately pushed out

[jira] [Reopened] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-862: Reopening at Nathan's suggestion that we may want to apply this to 2.x Rebuilding

[jira] [Resolved] (VELOCITY-861) Improve parser modification and build documentation

[ https://issues.apache.org/jira/browse/VELOCITY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-861. Resolution: Fixed Applied patch to 1.x trunk. Changed javacc4.2 version to 4.1

[jira] [Updated] (VELOCITY-861) Improve parser modification and build documentation

[ https://issues.apache.org/jira/browse/VELOCITY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-861: --- Affects Version/s: (was: 1.7) 1.x Improve parser

[jira] [Updated] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-862: --- Fix Version/s: 1.x Rebuilding parser using javacc 4.1 loses Node import

[jira] [Updated] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-862: --- Summary: Rebuilding parser using javacc 4.1 loses Node import (was: Rebuilding

[jira] [Updated] (VELOCITY-864) Download and install Apache Rat task in preparation target for ant rat

[ https://issues.apache.org/jira/browse/VELOCITY-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-864: --- Affects Version/s: (was: 1.7.x) 1.x Download

[jira] [Assigned] (VELOCITY-864) Download and install Apache Rat task in preparation target for ant rat

[ https://issues.apache.org/jira/browse/VELOCITY-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELOCITY-864: -- Assignee: Mike Kienenberger Download and install Apache Rat task

1.8-SNAPSHOT as version for 1.x pom.xml?

My maven knowledge is tragically small. Do we need to make the following change for the 1.x pom.xml? Index: pom.xml === --- pom.xml(revision 1683209) +++ pom.xml(working copy) @@ -33,7 +33,7 @@

Re: 1.8-SNAPSHOT as version for 1.x pom.xml?

. So yes, that needs to be changed. On 06/02/2015 10:52 PM, Mike Kienenberger wrote: My maven knowledge is tragically small. Do we need to make the following change for the 1.x pom.xml? Index: pom.xml === --- pom.xml(revision

Re: [jira] [Updated] (VELOCITY-864) Download and install Apache Rat task in preparation target for ant rat

rule? On 06/02/2015 10:53 PM, Mike Kienenberger (JIRA) wrote: Mike Kienenberger updated VELOCITY-864: --- Affects Version/s: (was: 1.7.x) 1.x -- Sergiu Dumitriu http://purl.org/net/sergiu

[jira] [Updated] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-862: --- Affects Version/s: (was: 1.x) Rebuilding parser using javacc 4.1 loses Node

[jira] [Updated] (VELOCITY-863) Regression: #settableft-paren no longer valid grammar

[ https://issues.apache.org/jira/browse/VELOCITY-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-863: --- Affects Version/s: (was: 1.7.x) Regression: #settableft-paren no longer valid

[jira] [Closed] (VELOCITY-846) Create a branch out of the 1.7 tag.

[ https://issues.apache.org/jira/browse/VELOCITY-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger closed VELOCITY-846. -- Might as well close this as there's nothing further to be done. Create a branch out

[jira] [Updated] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-816: --- Assignee: (was: Mike Kienenberger) Upgrade commons-lang from 2.4 to 2.6

[jira] [Resolved] (VELOCITY-862) Rebuilding parser using javacc 4.1 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-862. Resolution: Fixed Applied patch to 1.x trunk. Rebuilding parser using javacc

[jira] [Updated] (VELOCITY-863) Regression: #settableft-paren no longer valid grammar

[ https://issues.apache.org/jira/browse/VELOCITY-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-863: --- Fix Version/s: 1.x Regression: #settableft-paren no longer valid grammar

[jira] [Reopened] (VELOCITY-863) Regression: #settableft-paren no longer valid grammar

[ https://issues.apache.org/jira/browse/VELOCITY-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-863: Adding 1.x fix version Regression: #settableft-paren no longer valid grammar

[jira] [Resolved] (VELOCITY-863) Regression: #settableft-paren no longer valid grammar

[ https://issues.apache.org/jira/browse/VELOCITY-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-863. Resolution: Fixed Added 1.x fix version Regression: #settableft-paren no longer

Re: [jira] [Resolved] (VELOCITY-861) Improve parser modification and build documentation

I like to resolve when fixed in svn and to close when released. I think it's more meaningful. On Tue, Jun 2, 2015 at 10:30 PM, Sergiu Dumitriu sergiu.dumit...@gmail.com wrote: Should issues be Resolved or Closed? So far I've been closing them. On 06/02/2015 10:25 PM, Mike Kienenberger (JIRA

Re: svn commit: r1683210 - in /velocity/engine/branches/1.x: build/BUILD_PARSER_README.txt src/java/org/apache/velocity/runtime/parser/BUILD_README.txt src/java/org/apache/velocity/runtime/parser/buil

Yeah, that bothered me as well, but I'm no expert on the parser, so I didn't want to guess whether it was still applicable. If I didn't know, I left the original readme as-is. Java 3.1 has been required since 1.5, so it's been wrong for a long time. Please feel free to improve it further. On

[jira] [Resolved] (VELOCITY-864) Download and install Apache Rat task in preparation target for ant rat

[ https://issues.apache.org/jira/browse/VELOCITY-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-864. Resolution: Fixed Fix Version/s: 1.x Fixed in 1.x trunk. I couldn't apply

[jira] [Updated] (VELOCITY-864) Download and install Apache Rat task in preparation target for ant rat

[ https://issues.apache.org/jira/browse/VELOCITY-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-864: --- Affects Version/s: (was: 1.x) Download and install Apache Rat task

[jira] [Assigned] (VELOCITY-861) Improve parser modification and build documentation

[ https://issues.apache.org/jira/browse/VELOCITY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELOCITY-861: -- Assignee: Mike Kienenberger Improve parser modification and build

[jira] [Assigned] (VELOCITY-862) Rebuilding parser using javacc 4.2 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELOCITY-862: -- Assignee: Mike Kienenberger Rebuilding parser using javacc 4.2 loses Node

[jira] [Updated] (VELOCITY-862) Rebuilding parser using javacc 4.2 loses Node import

[ https://issues.apache.org/jira/browse/VELOCITY-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger updated VELOCITY-862: --- Affects Version/s: (was: 1.7) 1.x Rebuilding parser

[jira] [Reopened] (VELOCITY-860) Fix Velocity 1.7.x, 1.6.x, 1.5 ant download dependency build script

[ https://issues.apache.org/jira/browse/VELOCITY-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reopened VELOCITY-860: Adding 1.x fix version Fix Velocity 1.7.x, 1.6.x, 1.5 ant download dependency build

[jira] [Resolved] (VELOCITY-860) Fix Velocity 1.7.x, 1.6.x, 1.5 ant download dependency build script

[ https://issues.apache.org/jira/browse/VELOCITY-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger resolved VELOCITY-860. Resolution: Fixed Added 1.x fix version Fix Velocity 1.7.x, 1.6.x, 1.5 ant

Re: [jira] [Resolved] (VELOCITY-861) Improve parser modification and build documentation

, 2015 at 10:34 PM, Mike Kienenberger mkien...@gmail.com wrote: I like to resolve when fixed in svn and to close when released. I think it's more meaningful. On Tue, Jun 2, 2015 at 10:30 PM, Sergiu Dumitriu sergiu.dumit...@gmail.com wrote: Should issues be Resolved or Closed? So far I've been

Fixing build issues in 1.x but not 2.x

I hope it's not a problem, but I'm only applying the build process fixes to the 1.x branch and not the 2.x branch. My thinking is that the work has most likely already been done on 2.x, and I'm also not sure I have the time to invest in the 2.x branch. If you see something that you think I

[jira] [Assigned] (VELOCITY-816) Upgrade commons-lang from 2.4 to 2.6.

[ https://issues.apache.org/jira/browse/VELOCITY-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Kienenberger reassigned VELOCITY-816: -- Assignee: Mike Kienenberger Upgrade commons-lang from 2.4 to 2.6

Re: [jira] [Commented] (VELOCITY-818) Case-insensitive matching ${object.methodName} == ${object.methodname} == ${object.methodName}

Well, I'm ok if you want to reopen it and do something with it, but I don't want to leave people with false hope. I guess I can see why it might be helpful in some cases where a non-technical user may not understand the need for case-sensitivity. On Tue, Jun 2, 2015 at 11:38 PM, Sergiu Dumitriu

Changing velocity web site

I am looking at velocity/site to determine what the process is in order to update it. It looks like Daniel converted velocity to svnpubsub in 2014. I can't find a jira issue in INFRA or VELOCITY dealing with it, though. Which directory is the live version? velocity/site/production? I can

Re: svn commit: r1682680 - in /velocity/engine/branches/1.x/build: build.properties download.xml

...@apache.org wrote: Author: sdumitriu Date: Sun May 31 06:24:10 2015 New Revision: 1682680 URL: http://svn.apache.org/r1682680 Log: VELOCITY-860: Fix Velocity 1.7.x, 1.6.x, 1.5 ant download dependency build script Patch from Mike Kienenberger applied without changes Modified: velocity/engine

Re: svn commit: r1682669 - in /velocity/engine/trunk/velocity-engine-core/src: main/parser/Parser.jjt test/resources/set/set1.vm test/resources/set/set2.vm

: #settableft-paren no longer valid grammar Patch from Mike Kienenberger applied + added test Modified: velocity/engine/trunk/velocity-engine-core/src/main/parser/Parser.jjt velocity/engine/trunk/velocity-engine-core/src/test/resources/set/set1.vm velocity/engine/trunk/velocity-engine

Re: svn commit: r1682680 - in /velocity/engine/branches/1.x/build: build.properties download.xml

Thanks. Makes perfect sense now that you've said it :) On Sun, May 31, 2015 at 3:22 PM, Nathan Bubna nbu...@gmail.com wrote: The 1.x branch is the head of 1.x development. Effectively, it's what could become a 1.8 version. On Sun, May 31, 2015 at 10:15 AM, Mike Kienenberger mkien

Re: svn commit: r1682680 - in /velocity/engine/branches/1.x/build: build.properties download.xml

have one of those around. On 05/31/2015 01:15 PM, Mike Kienenberger wrote: What's the 1.x branch? We should also make sure that the 1.5 patch is applied to the Velocity_1.5_BRANCH branch so someone checking out from svn can at least build 1.5 from source, although, like 1.6, I doubt we

Recent JIRA issues (with patches) by me

Since I'm not certain who, if anyone, is notified of JIRA changes, here's a list of the items I've been working on. VELOCITY-864 Download and install Apache Rat task in preparation target for ant rat VELOCITY-863 Regression: #settableft-paren no longer valid grammar VELOCITY-862 Rebuilding parser

No JIRA changes sent to a mailing list?

I signed up for the commits mailing list, but as I was looking through the archives, I noticed that there's no JIRA change notifications sent to commit@, nor are they sent to dev@. Shouldn't these be going to a mailing list? How do you subscribe to JIRA changes?

general@velocity mailing list

And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that

Re: No JIRA changes sent to a mailing list?

must handle (cc-ing). Infra: for the VELOCITY jira project, the notification scheme must be changed to send emails to dev@velocity.apache.org instead of the defunct velocity-...@jakarta.apache.org (or should that be comm...@velocity.apache.org?) On 05/30/2015 06:54 AM, Mike Kienenberger

Re: Successfully building 1.x branches and regenerating parser files

On Thu, May 28, 2015 at 10:48 PM, Mike Kienenberger mkien...@gmail.com wrote: 1.3 and 1.4 won't build without some code changes -- they use enum as a variable. These were generated parser files. A find and replace of enum to enmr was all that was needed. Or going back to java 1.3 :) Parser

Re: Successfully building 1.x branches and regenerating parser files

build for the 1.7.x branch is actually quite easy, we could quickly fix a couple of things and release 1.7.1. Does any committer want to take the lead on that? On 05/29/2015 08:48 AM, Mike Kienenberger wrote: On Thu, May 28, 2015 at 10:48 PM, Mike Kienenberger mkien...@gmail.com wrote: 1.3

Re: Successfully building 1.x branches and regenerating parser files

I have created issues 861 (improve parser documentation) and 862 (fix parser import generation) to clean up the parser building process. https://issues.apache.org/jira/browse/VELOCITY-861 https://issues.apache.org/jira/browse/VELOCITY-862 On Fri, May 29, 2015 at 9:33 AM, Mike Kienenberger mkien

Re: Upgraded Commons and Velocity 2.0

On Fri, May 29, 2015 at 10:33 AM, Nathan Bubna nbu...@gmail.com wrote: If Mike wants to revive the Ant build for 1.7, i have no problem with that. I do remember the JJParserState issue when rebuilding the parser though. Always bugged me, but i never saw an easy fix. My first try at an easy fix

Minimum java version for a 1.8 branch?

I think we should also upgrade the minimum java version required for Velocity if we create a 1.8 branch. [javac] warning: [options] bootstrap class path not set in conjunction with -source 1.4 [javac] warning: [options] source value 1.4 is obsolete and will be removed in a future release

Re: Upgraded Commons and Velocity 2.0

On Fri, May 29, 2015 at 10:57 AM, Frederick N. Brier fnbr...@gmail.com wrote: I did a large amount of work last year on the Velocity 1.7 branch, split it into a main project and sub projects that integrated with other components, updated the packages, switched to slf4j and got it building under

Re: Upgraded Commons and Velocity 2.0

antonio.petre...@gmail.com wrote: 2015-05-29 17:21 GMT+02:00 Mike Kienenberger mkien...@gmail.com: I am also interested in SLF4J support (sorry, Chris, but if you're going to propose switching to commons-logging, you might as well go with SLF4J: http://www.slf4j.org/faq.html#why_new_project

Re: Successfully building 1.x branches and regenerating parser files

? Should I change my Maven build to regenerate the parser? Or is it enough that I pushed my code to Github. Thank you. Fred On 05/29/2015 06:59 AM, Mike Kienenberger wrote: I have created issues 861 (improve parser documentation) and 862 (fix parser import generation) to clean up the parser

  1   2   >