Re: [VOTE] Velocity Engine 2.4 Release Quality

Works well for me.  Thanks. On 12/09/2024 10:21, Claude Brisson wrote: If you have had a chance to review the test build, please respond with a vote on its quality:  [ ] Leave at test build  [ ] Alpha  [ ] Beta  [x] General Availability (GA) --

Re: [VOTE] Release Velocity Engine version 2.4.1

It passes all my tests, and works great.  Thanks. On 18/02/2024 12:45, Michael Osipov wrote: Hi, Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104&version=12354231 Staging repo: https://repository.apache.org/content/repositories/orgapachevelocity-1043/

WARNING: Illegal reflective access

Hello, I see this in my compile on java 11. WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl (file:~.m2/repository/org/apache/velocity/velocity-engine-core/2.3/velocity-engine

Re: [VOTE] Engine 2.3 RC1 Release quality

Just for the velocity-engine-core-2.3.jar, works ok for me. [x] General Availability (GA) Cheers Not sure if its my setup but I get for $ git clone --branch velocity-master-4 https://github.com/apache/velocity-master.git $ cd velocity-master $ mvn install [INFO] Scanning for projects

Re: [ANNOUCE] Velocity Engine 2.3 test build available

Previously I have used the below for maven, now I get [ERROR] Failed to execute goal on project events: Could not resolve dependencies for project my.war: Failed to collect dependencies at org.apache.velocity:velocity-engine-core:jar:2.3: Failed to read artifact descriptor for org.apache.velo

Re: [ANNOUNCE] Velocity Engine 2.2 RC6 test build available

Works well for me now. Thanks. On Thu, 30 Jan 2020 at 01:05, Claude Brisson wrote: > The test build of Velocity Engine 2.2 RC6 is available. > > No determination as to the quality ('alpha,' 'beta,' or 'GA') of > Velocity Engine 2.2 has been made, and at this time it is simply a "test > build".

Re: [ANNOUNCE] Velocity Engine 2.2 RC5 test build available

Hello, Checking this, I have an error where it does not render a parameter (generic variable) correctly ie $type: #showAutocomplete("$search/entry", '1', $name, 'query', false) #macro(showAutocomplete $sUrl $source $name $type $links) ... data: { sUrl: "$sUrl", source: "$sour

Re: [VOTE] Engine 2.2 RC1 Release quality

Works great for me. [ ] Leave at test build [ ] Alpha [ ] Beta [x] General Availability (GA) nb Thanks. On Fri, 20 Sep 2019 at 13:33, Claude Brisson wrote: > The Velocity Engine 2.2 RC1 is available since September 8. > > Main changes in this release: > > - New 1.7 backward compatibility

Re: [ANNOUCE] Velocity Engine 2.2 test build available

Works well for me. Thanks. On Sun, 8 Sep 2019 at 18:46, Claude Brisson wrote: > The test build of Velocity Engine 2.2 RC1 is available. > > No determination as to the quality ('alpha,' 'beta,' or 'GA') of > Velocity Engine 2.2 RC1 has been made, and at this time it is simply a > "test build". W

Re: [VOTE] Engine 2.1 RC3 Release quality

n? Well, this subproject has been archived, since no one is > maintaining it anymore. > > It shouldn't be too hard to patch it the day Engine 3.0 drops reprecated > config names, though. > > On 20/03/2019 09:39, Greg Huber wrote: > > I was just

Re: [VOTE] Engine 2.1 RC3 Release quality

I was just upgrading my local taxen task and it uses VelocityEngine.RESOURCE_LOADER with a value of resource.loader Maybe this need to be upgraded? >> resource.loaders as I get a message when running the command. [WARNING] configuration key 'resource.loader' has been deprecated in favor of 'resourc

Re: [VOTE] Engine 2.1 RC3 Release quality

Thanks for your effort, works great for me. [x] General Availability (GA) On Wed, 20 Mar 2019 at 00:43, Claude Brisson wrote: > The Velocity Engine 2.1 RC3 is available since March 15. > > Main changes: > > * Velocity Engine 2.1 now requires JDK 1.8+ > * Two more backward compatibility flag

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

t; > so that the logger is initialized first. > > I'll document that. > > If that didn't work, did you check that there wasn't an older > velocity-engine-core jar in the classpath? > > On 14/03/2019 17:42, Greg Huber wrote: > > Tomcat logs (would be th

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

inning of your web.xml file: > > > com.republicate.slf4j.impl.ServletContextLoggerListener > > > > > so that the logger is initialized first. > > I'll document that. > > If that didn't work, did you check that there wasn't an older > velocity-engine-core jar in the classpa

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

maven's? Most test cases logs > aren't visible in maven output. > > >Claude > > On 14/03/2019 10:56, Greg Huber wrote: > > Is there any way to check if the depreciated properties logging is > > working? I would have thought I would see some me

Re: [ANNOUNCE] Velocity Engine 2.1 RC2 test build available

Is there any way to check if the depreciated properties logging is working? I would have thought I would see some messages in the logs: eg for my resource.loader = webapp, my 2.0: webapp.resource.loader.description=Webapp Resource Loader 2.1 property name: resource.loader.. Cheers Greg O

Re: [jira] [Resolved] (VELTOOLS-169) Upgrade commons-collections compile dependency to v3.2.2 or v4.1

Claude, Thanks for the updates, btw the depreciated TexenTask also uses the ExtendedProperties, I tried to use the o.a.v.util.ExtProperties suggested here, but it does not work for some reason, I switched to org.apache.commons.configuration2.PropertiesConfiguration which does work. its basically

Re: [jira] [Commented] (VELOCITY-891) Upgrade to v2.0 causes parser failures

Have you tried {{#set ($JQId = '#' + $Utils.getJQuerySelector($SparklineElementId))}} eg #set ($ok = '#' + 'ok') $ok then outputs #ok #set ($ok = "#" + 'ok') gives Failed to parse String literal at 2f336dfc-5fee-4e00-a58d-1b5a54729690:standard[line 1, column 13] org.apache.velocity.

Re: [VOTE] Engine 2.0 RC9 Release quality

Works great for me. Thanks. [x] General Availability (GA) On 29 July 2017 at 00:00, Claude Brisson wrote: > The Velocity Engine 2.0 RC9 is available. > > Main change since the RC8 is a full review of the DataSourceResourceLoader. > > Release notes: > > * https://dist.apache.org/repos/dist/dev/

Re: [RESULT] [VOTE] Engine 2.0 RC8 Release quality

Maybe bump commons-lang3 to 3.6? Just released in June. Cheers Greg On 18 June 2017 at 22:13, Claude Brisson wrote: > I should be able to find the time, yes. > > Claude > > > On 18/06/2017 10:46, Michael Osipov wrote: > >> Am 2017-06-17 um 11:46 schrieb Claude Brisson: >> >>> Result: >>> >>>

Re: [VOTE] Engine 2.0 RC8 Release quality

Works well for me. Thanks. [ ] Leave at test build [ ] Alpha [ ] Beta [x] General Availability (GA) +1 (nb) On 1 May 2017 at 17:50, Claude Brisson wrote: > The Velocity Engine 2.0 RC8 is available. > > Main change since the RC6 is a rewrite of the methods disambiguation > algorithm. RC7

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

g() method, which should > not be used by Texe. > > On 27/04/2017 14:40, Greg Huber wrote: > >> Claude, >> >> I think I have managed to resolve it. Most of the methods in >> org.apache.velocity.util.StringUtils have been removed. Which texen >> relies >

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

RC with: > > svn export https://dist.apache.org/repos/ > dist/dev/velocity/velocity-engine/2.0/velocity-engine-core-2.0.jar@19088 > > here, for instance, 19088 corresponds to the RC7. > > > On 27/04/2017 12:31, Greg Huber wrote: > >> Well, I found a version dated 16th Nov

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Well, I found a version dated 16th November 2016, which does work so its not my setup. Will try and debug the ant process for any errors. On 14 April 2017 at 11:41, Claude Brisson wrote: > A new test build of Velocity Engine 2.0 is available (RC8). > > No determination as to the quality ('alpha

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

I have noticed now that my bespoke taxen generator does not produce any output. Also there are no errors generated. Is it possible to back to previous snapshots (rc1) to see if the problem exists? There seems to be only the lasted release in the repo. https://repository.apache.org/content/repos

Re: [ANNOUNCE] Velocity Engine 2.0 RC8 test build available

Works great for me +1. Cheers Greg On 14 April 2017 at 11:41, Claude Brisson wrote: > A new test build of Velocity Engine 2.0 is available (RC8). > > No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity > Engine 2.0 has been made, and at this time it is simply a "test build

Re: [ANNOUNCE] Velocity Engine 2.0 RC7 test build available

Works well for me. Thanks. On 9 April 2017 at 00:19, Claude Brisson wrote: > A new test build of Velocity Engine 2.0 is available (RC7). > > No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity > Engine 2.0 has been made, and at this time it is simply a "test build". We > w

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

rt org.apache.commons.io.FileUtils; >> >> String content = FiileUtils.readFileToString(new File(filename), >> Charset.UTF_8); >> >> The charset parameter is optional but recommended. Adapt it to your >> needs, of course. >> >> [1] https://mvnrepository.com/artifact

Re: [ANNOUNCE] Velocity Engine 2.0 RC6 test build available

Hello, I use the taxen task, and now have a local copy as its no longer supported. What would be an equivalent to .fileContentsToString(..) as its now missing? org.apache.velocity.util.StringUtils value = StringUtils.fileContentsToString( getProject().res

Re: [VOTE] Engine 2.0 RC5 Release quality

[ ] Leave at test build [ ] Alpha [ ] Beta [x] General Availability (GA) +1 works great for me. Thanks. On 16 January 2017 at 14:02, Claude Brisson wrote: > The Velocity Engine 2.0 RC5 is available. > > Main changes since the RC4: > > * the default encoding is now UTF-8 (and not the platform

Re: Reloading resources adding new macros

was not picking up the correct version. I should have checked it more before asking the question. Cheers Greg On 5 January 2017 at 16:28, Christopher Schultz < ch...@christopherschultz.net> wrote: > Greg, > > On 1/4/17 11:40 AM, Greg Huber wrote: > >> Velocity version? &

Re: Reloading resources adding new macros

.it does not remove macros names, will keep this in mind next time I do template work and work out exactly why I need to restart (if I still have to do it at all). Cheers Greg On 4 January 2017 at 17:34, Michael Osipov wrote: > Am 2017-01-04 um 14:43 schrieb Greg Huber: > >>

Re: Reloading resources adding new macros

Sorry, I have looked at this again and it does now reload correctly with the new macros without the restart. Please ignore my previous emails!! Cheers Greg. On 4 January 2017 at 17:34, Michael Osipov wrote: > Am 2017-01-04 um 14:43 schrieb Greg Huber: > >> The was one issue t

Re: Reloading resources adding new macros

If someone could point me in the right direction on where it reloads the macro names in the code, I could have a look myself at fixing it. Cheer Greg On 4 January 2017 at 17:34, Michael Osipov wrote: > Am 2017-01-04 um 14:43 schrieb Greg Huber: > >> The was one issue that has bee

Re: Reloading resources adding new macros

ed/reset when the macro is reloaded, but it looked much more complicated. Cheers Greg On 4 January 2017 at 17:34, Michael Osipov wrote: > Am 2017-01-04 um 14:43 schrieb Greg Huber: > >> The was one issue that has been around for ages, and I am not sure if it >> is >> pos

Re: Reloading resources adding new macros

return 0; } File cachedFile = getCachedFile(rootPath, resource.getName()); if (cachedFile.canRead()) { return cachedFile.lastModified(); } else { return 0; } } } On 4 January 2017 at 16:04, Christopher Schultz < c

Reloading resources adding new macros

The was one issue that has been around for ages, and I am not sure if it is possible to fix it. If I have added a new macro into a velocity template file loaded via a resource loader, I have to shut down the container (tomcat) and restart for it to be picked up. I will allow the contents of the m

Re: [ANNOUNCE] Velocity Engine 2.0 RC5 test build available

For this rc5 is says org.apache.velocity.runtime.resource.loader.ResourceLoader2; does not exist and ResourceLoader says its depreciated? Cheers Greg On 3 January 2017 at 23:43, Claude Brisson wrote: > A new test build of Velocity Engine 2.0 is available (RC5). > > No determination as to the

Re: [VOTE] 2.0 Release Quality

Thanks, works great for me. [x] General Availability (GA) +1 non binding. On 16 November 2016 at 11:51, Claude Brisson wrote: > The Velocity Engine 2.0 RC3 test build has been available since the 12th, > and the RC4 (which only contains trivial fixes) has just been published. > > Release note

Re: TexenTask

gt; > You may need to recompile it, but there are good chances that it sill > works with Velocity 2.0. > > > Claude > > > On 12/11/2016 12:38, Greg Huber wrote: > >> In my build I use velocity (ant) to generate some scripts and now its >> failing as the or

Re: [ANNOUNCE] Velocity Engine 2.0 RC3 test build available

Is the staging directory now orgapachevelocity-1012/ ? orgapachevelocity-1011 gives a 404 On 12 November 2016 at 21:15, Claude Brisson wrote: > A new test build of Velocity Engine 2.0 is available (RC3). > > No dete

TexenTask

In my build I use velocity (ant) to generate some scripts and now its failing as the org.apache.velocity.texen.ant.TexenTask is missing. Have or can these been added to another package? Cheers

Re: Logging configuration

; velocity.tools.[toolskey] instead of the tools class (which allows custom >> user tools to enter our hierarchy). >> >> Thoughts? >> >> Claude >> >> >> On 10/11/2016 17:18, Mike Kienenberger wrote: >> >>> +1 to using several appropriate

Re: Logging configuration

in Velocity (apart for the > Tools themselves). > > I chose to use the first variant for sobriety (to avoid each log line > contain the whole package name), but it s not necessarily a definitive > choice. At least, it should be better documented. > > Does your logging work properly

Logging configuration

The name needs to be exactly Velocity which is not what I had expected, usually its the package name format ie org.apache.velocity. the docs suggest its org.apache.velocity.app.Velocity This seems to be set in RuntimeInstance: private Logger log = LoggerFactory.getLogger("Velocit

Re: [ANNOUNCE] Velocity Engine 2.0 test build available

It happens when the method is overloaded with a >>> variant that takes no argument. >>> >>> Guess there will be a third release candidate... >>> >>> >>> >>> On 09/11/2016 17:44, Greg Huber wrote: >>> >>> It seems to b

Re: [ANNOUNCE] Velocity Engine 2.0 test build available

is overloaded with a > variant that takes no argument. > > Guess there will be a third release candidate... > > > On 09/11/2016 17:44, Greg Huber wrote: > >> It seems to be returning the wrong class name in ClassUtils >> >> method = node.getRuntimeServices()

Re: [ANNOUNCE] Velocity Engine 2.0 test build available

> > > On 09/11/2016 16:50, Greg Huber wrote: > >> Hello, >> >> I am getting an error when a parameter on a method name is null, it says >> "wrong number of arguments at" >> >> eg : >> >> $entry.filePath == nu

Re: [ANNOUNCE] Velocity Engine 2.0 test build available

09, Claude Brisson wrote: > I cannot reproduce it. > > Is the thumbResource() method overloaded? > > Do you have the full stacktrace? > > > On 09/11/2016 16:50, Greg Huber wrote: > >> Hello, >> >> I am getting an error when a parameter on a method

Re: [ANNOUNCE] Velocity Engine 2.0 test build available

Hello, I am getting an error when a parameter on a method name is null, it says "wrong number of arguments at" eg : $entry.filePath == null $myPojo.thumbResource($entry.name, $entry.filePath) I get an exception : java.lang.IllegalArgumentException: wrong number of arguments at.. public Str