[RESULT] [VOTE] Engine 2.0 RC8 Release quality

/browse/VELOCITY-880 On 01/05/2017 18: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 needed a bugfix and didn't reach the vote. Release notes: * https://dist.apache.org/repos/dist/dev/velocity

Re: Engine 2.0 release ?

We had two PCM +1s and needed a third one, which was on its way... but meanwhile a DataSourceResourceLoader issue came up, so we may want to fix it. I really hope to push it out very soon. On 14/06/2017 19:05, Alessio Soldano wrote: Hi, I'm wondering if the 2.0 release is actually going to

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

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: Two binding votes and two non-binding votes for GA. While at least two PMCs did express their will to vote, a user raised an issue about

[VOTE] Engine 2.0 RC8 Release quality

The Velocity Engine 2.0 RC8 is available. Main change since the RC6 is a rewrite of the methods disambiguation algorithm. RC7 needed a bugfix and didn't reach the vote. Release notes: * https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/release-notes.html Distribution:

Re: [VOTE] Engine 2.0 RC8 Release quality

Here's my vote. [ ] Leave at test build [ ] Alpha [ ] Beta [x] General Availability (GA) On 01/05/2017 18: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 needed a bugfix and didn't

Re: [tools 2.0] ValueParser.getStrings splits on comma?

(switching to dev list) It should be fixed, see commit 1806423. On 22/08/2017 16:58, Nathan Bubna wrote: Yeah, that's not ideal. You can configure the string delimiter in your tool config. But this seems like surprising behavior for a ParameterTool to have. The dangers of inheritance, i

Re: JIRA permissions

I don't have enough karma, but we should hear from Nathan. Also, I wouldn't mind being a JIRA admin on those projects... Claude On 08/12/2017 14:03, Michael Osipov wrote: Hi folks, can someone give me the permissions to administer VELOCITY and VELTOOLS? I'd like to clean up very old open

Re: JIRA permissions

, Nathan Bubna <nbu...@gmail.com> wrote: Good idea. I'll see what i can do. On Fri, Dec 8, 2017 at 5:54 AM, Claude Brisson <cla...@renegat.net.invalid wrote: I don't have enough karma, but we should hear from Nathan. Also, I wouldn't mind being a JIRA admin on those projects... Claude

Re: JIRA permissions

My bad again, I thought it was a doublon and deleted one, there was two in each... I deleted only one good one out of two... On 08/12/2017 21:37, Michael Osipov wrote: Am 2017-12-08 um 21:29 schrieb Nathan Bubna: Ah, seems there's two of you in JIRA (or at least two guys w/your name). I'd

Re: [tools] Running under a SecurityManager

, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Claude, On 3/21/18 8:25 PM, Claude Brisson wrote: Yes, it'd be great to soon release the tools since the engine is out. Apologies for not replying sooner. And yes, autoconfig hasn't to be the default. Why not starting

Re: [tools] Running under a SecurityManager

On 04/25/2018 07:43 PM, Michael Osipov wrote: Am 2018-03-22 um 01:25 schrieb Claude Brisson: Yes, it'd be great to soon release the tools since the engine is out. And yes, autoconfig hasn't to be the default. Why not starting with an empty toolbox by default if it eases things

Re: Cannot build Tools from trunk

It's running for me under java 8. Log for the cargo section copy pasted below. Is it a linux/windows cargo/jetty problem? I think it's running under a SecurityManager and the policy isn't allowing the "jetty.home" system property to be read. I hitted this error during development, and fixed

Re: Commens on VELTOOLS from trunk [1]

On 06/25/2018 06:59 PM, Michael Osipov wrote: Folks, release 3.0 is pending, I took some time to check the current project status. Here are my observations: * STATUS seems obsolete * WHY_THREE_JARS.txt seems obsolete * README.txt seems obsolete * ./test: this should be in src/test/resources

Re: Cannot build Tools from trunk

It's running for me under java 8. Log for the cargo section copy pasted below. Is it a linux/windows cargo/jetty problem? [INFO] --- cargo-maven2-plugin:1.6.8:start (start-server) @ velocity-tools-examples-showcase --- [INFO] [2.ContainerStartMojo] Resolved container artifact

Re: [tools] Running under a SecurityManager

with this policy file [1], Christopher, let me know if it does correspond to what you had in mind. [1] https://s.apache.org/fNYb   Claude On 05/07/2018 10:03 PM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Claude, On 3/21/18 8:25 PM, Claude Brisson wrote: Yes, it'd be great

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

Most probably, you have several instances of Velocity in your classpath, an 1.7 and an older one somewhere else. Claude On 12/01/2018 14:14, Alessio Soldano wrote: It would be great to know which version of JBossWS (which is where the org.jboss.ws*.* classes come) and/or Apache CXF is

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

On 12/01/2018 20:26, Bessie, Timothy wrote: Hi all, thanks for the response! My replies: Claude Brisson: Most probably, you have several instances of Velocity in your classpath, an 1.7 and an older one somewhere else. That's what I suspected at first as well; I testing by removing all

Re: Yet another issue cleanup

+1 to both. On 27/12/2017 12:47, Michael Osipov wrote: Am 2017-12-09 um 01:29 schrieb Nathan Bubna: On Fri, Dec 8, 2017 at 2:54 PM, Michael Osipov wrote: Hi folks, I have noticed that good bunch of Velocity 0 tickets have been rejected though fix version has been

Re: [tools] Running under a SecurityManager

: Thanks, Claude! This looks great! On Wed, Jun 20, 2018 at 5:50 PM Claude Brisson wrote: I reviewed the configuration process of the VelocityView, and it's now much pickier about files i/o (no more CWD accesses), plus doing sensible accesses via privileged actions. I activated Java Security

Re: [tools] Running under a SecurityManager

Any thoughts on this? From my side, apart from this potential point, the tools are ready. Claude On 22/03/2018 01:25, Claude Brisson wrote: Yes, it'd be great to soon release the tools since the engine is out. And yes, autoconfig hasn't to be the default. Why not starting with an empty

Re: [tools] Running under a SecurityManager

Yes, it'd be great to soon release the tools since the engine is out. And yes, autoconfig hasn't to be the default. Why not starting with an empty toolbox by default if it eases things for integrators. But there are two different things here: 1) *default* tools (loaded from tools.xml files

Re: Commens on VELTOOLS from trunk [1]

Thanks! On 06/28/2018 09:55 PM, Michael Osipov wrote: Am 2018-06-25 um 19:25 schrieb Claude Brisson: On 06/25/2018 06:59 PM, Michael Osipov wrote: Folks, release 3.0 is pending, I took some time to check the current project status. Here are my observations: * STATUS seems obsolete

Re: Cannot build Tools from trunk

*you* spotted the bug and the entire Cargo variables are /crap/, unusable for policy files. The produce is java.io.File#toString() which does not work for URIs. The output is "file:D:\Projects\veltools...". This is like MNG-6386. There is no way to fix that, but only in Cargo by adding to

Re: Roadmap to VELTOOLS 3.0

Hi. Thanks for your work on the POMs, Michael ! About json-simple :  - I'm not against relying on an external dependency rather than using shading, but github releases aren't directly available as maven dependencies, you have to use third party tools like jitpack. Or maybe I missed

[VOTE] Velocity Tools 3.0 Release Quality

The Velocity Tools 3.0 test build has been available since October 1st. Release notes: * https://dist.apache.org/repos/dist/dev/velocity/velocity-tools/3.0/release-notes.html Distribution:  * https://dist.apache.org/repos/dist/dev/velocity/velocity-tools/3.0/ Maven 2 staging repository:  

Re: [VOTE] Velocity Tools 3.0 Release Quality

Seems ok to me.  [x] General Availability (GA)   Claude - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org

Re: [VOTE] Velocity Tools 3.0 Release Quality

With 3 binding votes from Michael, Nathan and myself, it's a go for GA! Thanks for your help and your support. I'm pushing the release out. On 10/04/2018 05:08 PM, Claude Brisson wrote: The Velocity Tools 3.0 test build has been available since October 1st. Release notes: * https

[ANNOUNCE] Velocity Tools 3.0 released

The Apache Velocity team is pleased to announce the release of Velocity Tools 3.0 GA. Velocity Tools is a library of template tools and helpers to ease the use of the Apache Velocity template engine in standalone applications and in webapps. Velocity Tools 3.0 brings a few new context tools

Re: [VOTE] Release Velocity Master version 3

+1 for me On 09/23/2018 12:58 AM, Michael Osipov wrote: Hi, * reformatted the POM to a readible state * Apache Parent upgraded to 21 * added plugin management section for commonly used plugins Staging repo: https://repository.apache.org/content/repositories/orgapachevelocity-1021/

Re: Cache handling in DuckType

Thanks for the patch. It has been commited in the svn trunk branch (2.1-SNAPSHOT). Do you think there is any other precaution to take about this issue of class reloading, for instance in the introspection package? Or would there be any benefit to declare our own class loader to be able to

[ANNOUCE] Apache Velocity Engine 2.1 Released

The Apache Velocity community is pleased to announce the release of Apache Velocity Engine 2.1. The release is available for download at: https://velocity.apache.org/download.cgi#engine Apache Velocity is well-known in the Java field as a lightweight, easy-to-use templating library for

[RESULT] [VOTE] Engine 2.1 RC3 Release quality

Three binding votes from Nathan, Michael and myself in favor of GA, I'll push the release out!   Claude On 20/03/2019 16:02, Nathan Bubna wrote: [+1] GA On Tue, Mar 19, 2019 at 5:43 PM Claude Brisson wrote: The Velocity Engine 2.1 RC3 is available since March 15. Main changes

git migration

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

Re: git migration

On 05/04/2019 09:59, Michael Osipov wrote: Am 2019-04-05 um 06:54 schrieb Claude Brisson: What about moving to git? +1 from me Where did this request come from? What motivates this change for me, do you mean? Basically it's the local branches management which I find the most appealing

Re: Merging VELOCITY-892

11:22, Claude Brisson wrote: On 2/23/19 8:52 AM, Michael Osipov wrote: I think it is absolutely not our task to split strings for user's convenience. The next one will request another separator and so on. We should add at most a splitter tool. What we could do is to provide a new syntax

Re: [ANNOUNCE] Velocity Engine 2.1 test build available

On 03/03/2019 21:52, Claude Brisson wrote: Is this list complete? http://velocity.apache.org/engine/2.0/configuration.html Apart from 2.1 novelties, I'm quite sure, yes. All new ones are visible in http://velocity.apache.org/engine/devel/configuration.html It looks like this one

[engine] Configuration key names refactoring proposal

2.1 RC1 is history, 2.1 RC2 is on its way. Here is a proposal for the configuration keys refactoring: https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html Modify this proposal boils down to edit key name strings in org.apache.runtime.RuntimeConstants, the

Re: Merging VELOCITY-892

On 2/23/19 8:52 AM, Michael Osipov wrote: I think it is absolutely not our task to split strings for user's convenience. The next one will request another separator and so on. We should add at most a splitter tool. What we could do is to provide a new syntax: "$obj.foo([1,2,3,4,5])", but that

Merging VELOCITY-892

Hi all. The VELOCITY-892 branch contains a fix for the corresponding issue [1]. The purpose is to let the method arguments conversion handler manipulate the formal arguments types as java.lang.reflect.Type rather than java.lang.Class, so that when dealing with a method like   void foo(List

Re: [ANNOUNCE] Velocity Engine 2.1 test build available

20 have the expected behavior (it does not enter the if and the boolean is based on "runtime.references.strict" property). It seems to just be missing a if on strictRef value. Tell me if I should create an issue on https://issues.apache.org/jira/browse/VELOCITY. On Mon, Mar 4, 2019 at 2:47 AM

[ANNOUNCE] Velocity Engine 2.1 test build available

The test build of Velocity Engine 2.1 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote

Re: [ANNOUNCE] Velocity Engine 2.1 test build available

On 03/03/2019 20:09, Michael Osipov wrote: I have noticed that too actually. I always wondered about this quirk: resource.loader = file,classpath,etc. file.resource.loader.path = ... instead of resource.loaders = file,classpath resource.loader.file.path = More standard, I agree.

Re: [ANNOUNCE] Velocity Engine 2.1 test build available

Thanks for the diligent feedback. Going through the notes makes make stumble upon this: Added a new 'parser.allows.dash.in.identifiers' boolean property (false per default) to (dis)allow '-' in reference identifiers . Fixes VELOCITY-542. I see a few issues here: * The property name is

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

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 On Mon, 11 Mar 2019 at 12:28, Claude Brisson wrote: The test build of Velocity Engine 2.1 RC2 is available

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

(would be the most useful). I know the logging works because if there is an invalid #if I get a log message. On Thu, 14 Mar 2019 at 16:31, Claude Brisson wrote: I would say yes, since most test cases still use the deprecated properties. One of the test cases explicitly checks for the warning

Re: [engine] Configuration key names refactoring proposal

On 09/03/2019 19:05, Michael Osipov wrote: Am 2019-03-07 um 01:16 schrieb Claude Brisson: 2.1 RC1 is history, 2.1 RC2 is on its way. Here is a proposal for the configuration keys refactoring: https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html Claude, I

[ANNOUNCE] Velocity Engine 2.1 RC2 test build available

The test build of Velocity Engine 2.1 RC2 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 RC2 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a

[VOTE] Engine 2.1 RC3 Release quality

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 flags with 1.7: hyphens in identifiers and macros literal arguments handling  * New VTL syntax: default values for references: ${name|'John

Re: [VOTE] Engine 2.1 RC3 Release quality

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 'resource.loaders' On Wed, 20 Mar 2019 at 00:43, Claude B

Re: [VOTE] Engine 2.1 RC3 Release quality

 [ ] Leave at test build  [ ] Alpha  [ ] Beta  [x] General Availability (GA) - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org

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

h I don't see listed in https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html. This property was unused. It has simply been removed. Maybe it should only have been deprecated. I'll mention it in the changes table.   Claude On Mon, Mar 11, 2019 at 1:28 PM Claude B

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

not logging. On Thu, 14 Mar 2019 at 19:35, Claude Brisson wrote: Those logs are emitted quite early in the webapp initialization. So chances are the logger is initialized afterwards. If you are using the webapp-slf4j-logger to forwards slf4j logs towards tomcat, be sure to: - use the latest version

velocity-tool-model submodule

Hi all. I have pushed in the 'model' branch a proposal for the velocity-tools-model submodule, which is a complete rewrite of my good old Velosurf library. The rationale is to be able to define and expose a model to the view layer:  - the model definition gathers entities and their

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

3/2019 17:42, Greg Huber wrote: Tomcat logs (would be the most useful). I know the logging works because if there is an invalid #if I get a log message. On Thu, 14 Mar 2019 at 16:31, Claude Brisson I would say yes, since most test cases still use the deprecated properties. One of the test cases exp

[ANNOUNCE] Velocity Engine 2.1 RC3 test build available

The test build of Velocity Engine 2.1 RC3 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 RC3 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a

Re: Velocity + Spring MVC

Hi. We are aware of the situation, and we were more or less expecting someone to make such a proposal. Yes, it will benefit both communities. +1 for me. I guess that if your patch includes proper test cases, support won't be problematic.   Claude On 01/06/2019 02:32, Brent Putman wrote:

Merging of VELOCITY-917

FYI, I'm about to merge the parser_experiments branch, see https://issues.apache.org/jira/browse/VELOCITY-917 and https://github.com/apache/velocity-engine/compare/parser_experiments . What it does: - introduce a Parser interface and patch the javacc generated files so that the generated

Re: Merging of VELOCITY-917

EST.MF does not exist. It does so even if I try to have maven-jar-plugin skip parent configuration.   --   Claude On 11/06/2019 16:51, Claude Brisson wrote: Of course ! On 11/06/2019 15:09, Michael Osipov wrote: Am 2019-06-11 um 13:32 schrieb Claude Brisson: FYI, I'm about to merge the parser

[ANNOUCE] Velocity Engine 2.2 test build available

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". We welcome any comments you may have, and will take all feedback into account if a

Re: [VOTE] Engine 2.2 RC1 Release quality

, 2019 at 5:33 AM Claude Brisson The Velocity Engine 2.2 RC1 is available since September 8. Main changes in this release: - New 1.7 backward compatibility flags to mimic 1.7.x InvalidReferenceHandler behavior. - New runtime.log.track_locations debugging configuration flag which displays

[VOTE] Engine 2.2 RC1 Release quality

The Velocity Engine 2.2 RC1 is available since September 8. Main changes in this release:  - New 1.7 backward compatibility flags to mimic 1.7.x InvalidReferenceHandler behavior.  - New runtime.log.track_locations debugging configuration flag which displays the VTL stack trace in the logs in

Re: [VOTE] Engine 2.2 RC1 Release quality

The Velocity Engine 2.2 RC1 is available since September 8.  [ ] Leave at test build  [ ] Alpha  [ ] Beta  [X] General Availability (GA)   Claude - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional

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

t;, source: "1", name: "homepage", $type: input.val() $type is used extensively as a generic variable, so maybe there is some clash somewhere? Also if I rename the variable, for example $type1, it seems to work. I Also went back to 2.1 to check and it works as expected. Cheer

[ANNOUNCE] Velocity Engine 2.2 RC6 test build available

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". We welcome any comments you may have, and will take all feedback into account if a quality

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

+1 On 20-01-30 02 h 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". We welcome any comments yo

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

the release in Maven Central very soon. Every kind of help is welcome in spreading the word about the new release.   --   Claude On 20-02-02 10 h 13, Greg Huber wrote: 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

[ANNOUCE] Apache Velocity Engine 2.2 Released

The Apache Velocity community is pleased to announce the release of Apache Velocity Engine 2.2. The release is available for download at: https://velocity.apache.org/download.cgi#engine Apache Velocity is well-known in the Java field as a lightweight, easy-to-use templating library for

Re: Problems with commons-beanutils-1.9.4

On 20-02-06 16 h 15, Christopher Schultz wrote: 3.0 completely dropped support for Struts, which is a requirement for me, so I don't have any current stake in velocity-tools 3.0. I'm happy to do the work (delete 4 lines of code; document; commit) but I won't have anything to test it with other

Re: Problems with commons-beanutils-1.9.4

Hi. I suspect the class= problem only happens when running under a security manager. I had set up the cargo maven plugin to run the showcase example under a security manager, but it was failing under window so for now it's commented in the showcase pom file. There are several other problems

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

ache.org/jira/browse/VELOCITY-924. On Wed, Jan 1, 2020 at 11:12 PM Claude Brisson wrote: The test build of Velocity Engine 2.2 RC4 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 RC3 has been made, and at this time it is simpl

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

Let us summarize the behavior in question. You have a template A which calls a macro M which in turn calls a template B. A defines $foo, B changes its value, and you want the new value to be visible in A but not in M. Is that right? Not quite. In Velocity 1.7 unless M also sets this value

[ANNOUNCE] Velocity Engine 2.2 RC4 test build available

The test build of Velocity Engine 2.2 RC4 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 RC3 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a

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

does not feels like what you were referring to. On Sat, Dec 28, 2019 at 2:11 PM Claude Brisson wrote: The test build of Velocity Engine 2.2 RC3 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.1 RC3 has been made, and at this time it is simply

Re: Using Velocity with GitHub

@Will - we are experiencing some troubles with the syncing of our github repository, we're investigating. @Konstantin - last release is very recent, and the 2.x series has bought up several new features like space gobbling, optimizations, syntax enhancements... And while it's true that

Re: Github sync with svn

Hi. The switch to git is complete, and there won't be any mirroring back to svn. I procrastinated doing an official communication on @dev about it. So here it is: Velocity development now happens on the Apache git server, dual-synced with github. Gitbox repositories :

Re: Use of external DTDs - CVE-2020-10683

Hi. Velocity Tools 3.x doesn't use dom4j anymore, only the standard javax.xml API. And external DTDs are already disallowed, see XmlUtils

Default github branches

Hi folks. I recently opened a routine ticket to infra to have the default github branch of apache/velocity-site moved from trunk to master (a change which is already effective in our other projects) : https://issues.apache.org/jira/browse/INFRA-21355 But I was asked in return to discuss

Re: 1.7.x backport for [SecureUberspector should block methods on ClassLoader and subclasses]

If I go to this page:     https://wiki.shibboleth.net/confluence/display/OS30/Home the first thing I see is the not at the top which states:     "The OpenSAML 3 software has reached its End of Life and is no longer supported. This space is available for historical purposes only." So why

Re: Resigning from Apache Velocity PMC

Thanks for all, Will. On 2021-03-11 23 h 03, Nathan Bubna wrote: Agreed. Thanks for your long work here, Will. If you're ever in Portland, drop me a line and i'll buy you a drink. :) On Thu, Mar 11, 2021 at 12:11 PM Henning Schmiedehausen < henn...@schmiedehausen.org> wrote: Will, Thank you

Re: need help with site update

Merged and publish. By the way, it's maybe a good time to recall everyone that site publishing is really easy now that it has been dockerized, and it boils down to calling a single shell script. See this doc: http://velocity.apache.org/site-building.html#building-the-site-with-docker On

Re: [VOTE] Engine 2.3 RC1 Release quality

. But Java is far from "legacy". It is still way younger than C++ and no one would call that "legacy". :-) -h On Wed, Mar 3, 2021 at 2:36 AM Claude Brisson wrote: Thanks for the review, Henning. I found a little bug myself, I was considering putting it aside f

[ANNOUNCE] Velocity Tools 3.1 test build available (RC1)

The test build of Velocity Tools 3.1 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Tools 3.0 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote

[ANNOUNCE] Velocity Tools 3.1 test build available (RC1)

The test build of Velocity Tools 3.1 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Tools 3.1 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a quality vote

Re: [ANNOUCE] Velocity Engine 2.3 test build available

This page lists two main changes: - Fix a minor security issue in user-edited templates applications: let SecureUberspector block methods on ClassLoader and subclasses. - New spring-velocity-support module for Velocity Engine integration in Spring Framework. but the linked

Re: [ANNOUCE] Velocity Engine 2.3 test build available

       always                 warn                                         true                 always                 warn                         org.apache.velocity velocity-engine-core             2.3 Any ideas, I have removed the .m2 velocity folder before the build. On 27/02/2021

[VOTE] Tools 3.1 RC1 Release quality

The Velocity Tools 3.1 RC1 is available since February 27. Main changes in this release: + Added an optional 'factory' attribute to tools with the classname of a factory for creating new tools instances + Added a new BreadcrumbTool meant to help displaying UI breadcrumb trails + Fix potential

Re: [VOTE] Tools 3.1 RC1 Release quality

+1 for GA On 21-03-01 21 h 26, Claude Brisson wrote: The Velocity Tools 3.1 RC1 is available since February 27. Main changes in this release: + Added an optional 'factory' attribute to tools with the classname of a factory for creating new tools instances + Added a new BreadcrumbTool meant

Re: [ANNOUCE] Velocity Engine 2.3 test build available

to date changelog on github: https://github.com/apache/velocity-engine/blob/master/src/changes/changes.xml On 21-03-01 02 h 52, Nate Chadwick wrote: It would be helpful to know the change list. Even if it is XML format could you attach? -n On Sun, Feb 28, 2021 at 3:24 PM Claude Brisson wrote

[RESULT] [VOTE] Release Velocity Master version 4

Five binding +1s, one non-binding +1. It's a go. On 2021-02-27 11 h 15, Claude Brisson wrote: Hi. Here's an RC for velocity-master-4, with the following changes: + set maven-enforcer-plugin and extra-enforcer-rules plugins versions + removed Antonio as emeritus, as per his request + switched

[RESULT] [VOTE] Engine 2.3 RC2 Release quality

Five binding +1 for GA. Release is underway. On 2021-03-03 13 h 29, Claude Brisson wrote: The Velocity Engine 2.3 RC2 is available since February 27. Main changes in this release: + New spring-velocity-support module, containing Spring framework Velocity Engine integration classes

[RESULT] [VOTE] Tools 3.1 RC1 Release quality

Six binding +1 for GA. A record! On 2021-03-01 21 h 26, Claude Brisson wrote: The Velocity Tools 3.1 RC1 is available since February 27. Main changes in this release: + Added an optional 'factory' attribute to tools with the classname of a factory for creating new tools instances + Added

Re: [VOTE] Engine 2.3 RC2 Release quality

+1 for GA. On 21-03-03 13 h 29, Claude Brisson wrote: The Velocity Engine 2.3 RC2 is available since February 27. Main changes in this release: + New spring-velocity-support module, containing Spring framework Velocity Engine integration classes. + Security fix: let SecureUberspector block

Re: [VOTE] Engine 2.3 RC1 Release quality

that Apache is commit-then-review, but hey, github. -h (First PR to velocity in ages. :-) ) On Mon, Mar 1, 2021 at 8:06 AM Claude Brisson wrote: The Velocity Engine 2.3 RC1 is available since February 27. Main changes in this release: + New spring-velocity-support module, containing

[VOTE] Engine 2.3 RC2 Release quality

The Velocity Engine 2.3 RC2 is available since February 27. Main changes in this release: + New spring-velocity-support module, containing Spring framework Velocity Engine integration classes. + Security fix: let SecureUberspector block methods on ClassLoader and subclasses. Changes from

[ANNOUNCE] Velocity Tools 3.1 released

The Apache Velocity team is pleased to announce the release of Velocity Tools 3.1. Velocity Tools is a library of template tools and helpers to ease the use of the Apache Velocity template engine in standalone applications and webapps. Main changes in this release: * Added an optional

Re: [VOTE] Release Velocity Master version 4

+1 On 21-02-27 11 h 15, Claude Brisson wrote: Hi. Here's an RC for velocity-master-4, with the following changes: + set maven-enforcer-plugin and extra-enforcer-rules plugins versions + removed Antonio as emeritus, as per his request + switched scm URLs from svn to git + added README.md file

[ANNOUCE] Velocity Engine 2.3 test build available

The test build of Velocity Engine 2.3 RC1 is available. No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity Engine 2.3 RC1 has been made, and at this time it is simply a "test build". We welcome any comments you may have, and will take all feedback into account if a

[VOTE] Release Velocity Master version 4

Hi. Here's an RC for velocity-master-4, with the following changes: + set maven-enforcer-plugin and extra-enforcer-rules plugins versions + removed Antonio as emeritus, as per his request + switched scm URLs from svn to git + added README.md file + updated apache parent to 23 Staging repo:

Fwd: Broken: apache/velocity-engine#21 (master - 1a22c95)

me clock icon1 min and 15 secs Claude Brisson avatarClaude Brisson 1a22c95 CHANGESET → <https://github.com/apache/velocity-engine/compare/aade2612b1f9...1a22c9542718> [engine] Anticipate master version increment Want to know about upcoming build environment updates? Would you

[VOTE] Engine 2.3 RC1 Release quality

The Velocity Engine 2.3 RC1 is available since February 27. Main changes in this release: + New spring-velocity-support module, containing Spring framework Velocity Engine integration classes. + Security fix: let SecureUberspector block methods on ClassLoader and subclasses. Release notes:

<    1   2   3   4   5   6   7   8   9   10   >