$!foo" == "").
Claude
On 06/02/2017 19:55, Michael Osipov wrote:
Am 2017-02-06 um 19:45 schrieb Nathan Bubna:
On Mon, Feb 6, 2017 at 10:32 AM, Michael Osipov <micha...@apache.org>
wrote:
Am 2017-02-06 um 19:23 schrieb Nathan Bubna:
On Mon, Feb 6, 2017 at 9:43 AM, Michael Osipov <mi
Am 2017-02-06 um 19:23 schrieb Nathan Bubna:
On Mon, Feb 6, 2017 at 9:43 AM, Michael Osipov <micha...@apache.org> wrote:
7) check object for a length() or size() method, if so return whether it
returns 0, but I agree with Alex Fedotov that we could skip those
methods if we already too
Am 2017-02-06 um 19:45 schrieb Nathan Bubna:
On Mon, Feb 6, 2017 at 10:32 AM, Michael Osipov <micha...@apache.org> wrote:
Am 2017-02-06 um 19:23 schrieb Nathan Bubna:
On Mon, Feb 6, 2017 at 9:43 AM, Michael Osipov <micha...@apache.org>
wrote:
7) check object for a length() or s
Hi Claude,
Am 2017-02-06 um 17:55 schrieb Claude Brisson:
Hi Christopher.
The spec has evolved quite a bit since then: the course I've taken is
this one (and remarks are welcome):
4) check for empty objects by class:
- return whether the collection is empty for a Collection object
5) check
Am 2017-01-20 um 22:15 schrieb Sergiu Dumitriu:
On 01/16/2017 08:56 AM, cbris...@apache.org wrote:
+ Michael Obispov suggested this example:
That would be "Osipov"...
Good catch, multumesc!
-
To unsubscribe, e-mail:
Am 2017-01-26 um 04:39 schrieb Claude Brisson:
A new test build of Velocity Engine 2.0 is available (RC6).
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 welcome any comments you may have, and
Am 2017-01-26 um 18:37 schrieb Claude Brisson:
Now my question is: do you or someone else think that the OSGi missing
meta-informations are a show stopper for the 2.0? Otherwise, my plan
is to open JIRA issues for all those remarks, try to release the RC6,
and handle the issues in 2.0.1 or
Am 2017-01-26 um 17:54 schrieb Claude Brisson:
On 26/01/2017 14:11, Michael Osipov wrote:
[...]
* StringUtils#normalizePath() can likely be replaced with Common IO's
FilenameUtils#normalize()
If we take this route, then we'll shade the commons-io class.
Absolutely, they might be other spots
Am 2017-01-27 um 00:27 schrieb Claude Brisson:
On 26/01/2017 19:45, Michael Osipov wrote:
Am 2017-01-26 um 18:37 schrieb Claude Brisson:
Now my question is: do you or someone else think that the OSGi missing
meta-informations are a show stopper for the 2.0? Otherwise, my plan
is to open
Am 2017-01-16 um 15:02 schrieb Claude Brisson:
The Velocity Engine 2.0 RC5 is available.
Main changes since the RC4:
* the default encoding is now UTF-8 (and not the platform default)
* commons-collections is not any more a compilation dependency
* commons-lang3 dependency is not any more
Am 2017-01-16 um 22:56 schrieb Claude Brisson:
That was fast.
On 16/01/2017 22:29, Michael Osipov wrote:
Here are my comments referred in my the previous mail:
* POM: use of JavaCC Maven Plugin: never ever add auto-generated code
to src/, it completely breaks
the agreed convention. Have
Am 2017-01-16 um 15:02 schrieb Claude Brisson:
The Velocity Engine 2.0 RC5 is available.
Main changes since the RC4:
* the default encoding is now UTF-8 (and not the platform default)
* commons-collections is not any more a compilation dependency
* commons-lang3 dependency is not any more
Am 2016-11-24 um 17:40 schrieb Sergiu Dumitriu:
On 11/24/2016 02:29 AM, Claude Brisson wrote:
6. I consider 435 to 441 being inconsisting to their counterpart 420
to 423.
Oh, you're speaking about line numbers in ConversionUtils.java... why is
it inconsistent? When we're speaking about date
Am 2016-11-24 um 08:29 schrieb Claude Brisson:
Glad to receive an enlightened opinion on the subject.
4. "-MM-dd'T'HH:mm:ssX and "-MM-dd HH:mm:ssX" are incomplete
if you have offsets by 30 or 45 minutes. You are simply truncating
them. Unless you know and you probably don't, always
the commit. The new code looks really great now, clean and
consistent. However, the comments have a few typos: ISO-8601, ISO 88601.
Replace it with "ISO 8601" and you are done.
Thanks for making Velocity even better...
Merci,
Michael
On 26/11/2016 02:08, Michael Osipov wrote:
Am 201
Hi folks,
based on VELOCITY-878 I am confused why this shading approach has been
taken?
1. Commons Lang 3: I see no benefit in shading it at all, if you check
the shaded JAR, a huge amount of classes are shaded. Moreover, Commons
Lang is so popular that most projects will include it in
Am 2016-12-09 um 16:10 schrieb Claude Brisson:
Hi.
On 09/12/2016 15:34, Michael Osipov wrote:
Hi folks,
the default encoding has been changed recently to UTF-8 [1], though I
still think that it requires some more description from a user's point
of view and more code cleanup
Feel free
Am 2016-12-09 um 13:05 schrieb Claude Brisson:
This issue has revealed another problem: we still have deprecated
initialization methods taking an ExtendedProperties object. But I had
totally overlooked the fact that since we now use shading, the method
signatures will change anyway. Even if we
Hi folks,
the default encoding has been changed recently to UTF-8 [1], though I
still think that it requires some more description from a user's point
of view and more code cleanup
* All templates (!) (anything else?) from ImputStream are read with that
new input encoding, unless other
Am 2016-12-09 um 18:26 schrieb Claude Brisson:
On 09/12/2016 16:39, Michael Osipov wrote:
[...]
* All templates (!) (anything else?) from ImputStream are read with
that new input encoding, unless other stated
That's all, except a resource can also be a static text file, as in
#include('file
Hi Claude,
did you get a change to read my comments to your recent changes on
GitHub? Haven't receive any feedback fron you yet.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands,
This time, it's about tools reading external resources. I'd like to:
1) have ImportSupport and ImportTool also be available in generic tools
for absolute URLs, only the view versions being able to import a
relative URL
2) have XmlTool inherit from ImportSupport, to homogenize its behavior
with
Am 2016-12-02 um 10:01 schrieb Claude Brisson:
Hi.
On 01/12/2016 21:21, Michael Osipov wrote:
While I understand you idea, I do think that introducing stuff like
this a bad idea for several reasons:
1. Processing of structured, low-level data like XML, JSON, form data
always belongs
Am 2017-01-03 um 16:43 schrieb Sergiu Dumitriu:
On 01/03/2017 09:09 AM, cbris...@apache.org wrote:
Author: cbrisson
Date: Tue Jan 3 14:09:41 2017
New Revision: 1777124
URL: http://svn.apache.org/viewvc?rev=1777124=rev
Log:
[site] fix two broken links
Modified:
Am 2017-04-09 um 01:19 schrieb Claude Brisson:
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 welcome any comments you may have, and
Am 2017-07-29 um 01:00 schrieb Claude Brisson:
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
[ ] General Availability (GA)
This is GA for me. Thanks for the great collaboration. I think I will
Am 2017-08-09 um 12:52 schrieb Claude Brisson:
The Apache Velocity community is pleased to announce the release of
Apache Velocity Engine 2.0. 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
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 the DataSourceResourceLoader [1] before they do so.
So let's hit the road again for another RC.
Am 2017-05-01 um 18:50 schrieb Claude Brisson:
The Velocity Engine 2.0 RC8 is available.
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[X] General Availability (GA)
Good work!
-
To unsubscribe, e-mail:
Hi folks,
can someone give me the permissions to administer VELOCITY and VELTOOLS?
I'd like to clean up very old open issues and focus and Velocity Tools 3.0.
Michael
-
To unsubscribe, e-mail:
Am 2017-12-08 um 16:00 schrieb Nathan Bubna:
Claude i think you should have the karma, if i'm reading things right; you
were already in the Administrators role. Michael, you are now too.
If i'm wrong, do let me know. We'll figure it out.
Thanks Nathan, works like a charm.
Hi folks,
I have noticed that good bunch of Velocity 0 tickets have been rejected
though fix version has been set. This is confusing for me and likely
others. Any reasoning behind this? Fix version implies that this one is
fixed at some point, not rejected for version x.
Any objections to
Am 2017-12-08 um 16:00 schrieb Nathan Bubna:
Claude i think you should have the karma, if i'm reading things right; you
were already in the Administrators role. Michael, you are now too.
If i'm wrong, do let me know. We'll figure it out.
Just rechecked. The role applies to VELTOOLS only. Can
Hi folks,
since Velocity Tools will be released soon, is anyone able to properly
consolidate tickets from 2.0.x, 2.1 and 2.x to version 3.0?
Query:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20VELTOOLS%20AND%20fixVersion%20in%20(2.0%2C%202.x%2C%202.1)
After that, I'd like to
nbu...@gmail.com> wrote:
I think i did add you to VELOCITY also. I'll double check.
On Fri, Dec 8, 2017 at 12:21 PM, Michael Osipov <micha...@apache.org>
wrote:
Am 2017-12-08 um 16:00 schrieb Nathan Bubna:
Claude i think you should have the karma, if i'm reading things right;
you
Am 2018-06-27 um 20:34 schrieb Claude Brisson:
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
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 somewhere
* there are a lot of empty dirs: still
Folks,
who is able to Tools from trunk?
I cannot with Java 8 and 10:
[INFO] --- cargo-maven2-plugin:1.6.8:start (start-server) @
velocity-tools-examples-showcase ---
[INFO] [2.ContainerStartMojo] Resolved container artifact
org.codehaus.cargo:cargo-core-container-jetty:jar:1.6.8 for
Am 2017-12-09 um 01:29 schrieb Nathan Bubna:
On Fri, Dec 8, 2017 at 2:54 PM, Michael Osipov <micha...@apache.org> wrote:
Hi folks,
I have noticed that good bunch of Velocity 0 tickets have been rejected
though fix version has been set. This is confusing for me and likely
others. Any rea
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 for integrators. But there
are two different things here:
1)
alking 2.x, then adding a PrivilegedAction sounds better.
If 3.0
(which, i think needs to happen anyway, right Claude?), then i'd
agree with
Michael. The auto config would be better off as something users need to
explicitly turn on, not the default any longer.
On Wed, Mar 21, 2018 at 2:03 PM, Michael Osi
Am 2018-03-21 um 06:17 schrieb Christopher Schultz:
All,
Using velocity-tools 2.0.
I've been exploring what it takes to get my application working under a
SecurityManager and it seems that o.a.v.t.view.VelocityView tries to
load a few configuration files from their default locations even when
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
* WHY_THREE_JARS.txt seems obsolete
* README.txt seems obsolete
Am 2018-06-28 um 14:34 schrieb Claude Brisson:
*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
As promised a few (non-exhaustive) comments on source and POMs:
* Serializable tools don't have a serialVersionUID
* A lot of code does not use generics
* Boilerplate code which can be replaced with Commons Lang 3, e.g.,
Verify, ClassUtils, StringUtils. Engine relies on it anyway.
* There is
Hi Claude,
the new GH fork is on Central:
https://search.maven.org/artifact/com.github.cliftonlabs/json-simple/3.0.2/jar
I'd use that. You are right, of course, about the library size which I
did not check. It so small that is not worth the hassle to be optional
or shaded. We can simply
So I have committed a branch for JSON stuff. Have a look. Looks straight
forward to me.
Michael
Am 2018-09-30 um 18:42 schrieb Claude Brisson:
> Hi.
>
> Thanks for your work on the POMs, Michael !
>
> About json-simple :
>
> - I'm not against relying on an external dependency rather than
Am 2018-09-30 um 08:33 schrieb Michael Osipov:
Folks,
how close are we to verion 3.0, what is holding us off?
I'd like to fix (VELTOOLS-174), VELTOOLS-178, and VELTOOLS-179 while
Claude should take a look at VELTOOLS-162/-174 and we are set. Some docs
and READMEs need an update too.
All
Am 2018-10-01 um 22:35 schrieb Claude Brisson:
The test build of Velocity Tools 3.0 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
Folks,
how close are we to verion 3.0, what is holding us off?
I'd like to fix (VELTOOLS-174), VELTOOLS-178, and VELTOOLS-179 while
Claude should take a look at VELTOOLS-162/-174 and we are set. Some docs
and READMEs need an update too.
Did I miss something?
Michael
Am 2018-10-04 um 17:08 schrieb Claude Brisson:
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:
*
Hi,
The vote has passed with the following result:
+1 (binding): Nathan Bubna, Claude Brisson, Will Glass-Husain, Michael
Osipov
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr
Am 2018-09-23 um 00:58 schrieb Michael Osipov:
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/
https
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/
Am 2019-04-05 um 06:54 schrieb Claude Brisson:
What about moving to git?
+1 from me
Where did this request come from?
I wouldn't mind that. We need to discuss which repos and how many we
need. Git isn't Subversion. Though, I am fine with both.
Michael
Am 2019-03-03 um 16:17 schrieb Claude Brisson:
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
Am 2019-03-03 um 19:29 schrieb Claude Brisson:
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
Am 2019-02-23 um 00:40 schrieb Claude Brisson:
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
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 like the proposal a lot. A very neat rework!
Am 2019-03-20 um 01:42 schrieb Claude Brisson:
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
Am 2019-03-07 um 13:08 schrieb Claude Brisson:
The StringEscapeUtils class is moving from commons-lang3 to commons-text.
We are using it in several reference insertion event handlers (to escape
xml, javascript or html).
For now the commons-lang3 version is still there, but deprecated. We
Am 2019-06-03 um 08:02 schrieb Brent Putman:
On 6/1/19 12:25 PM, Nathan Bubna wrote:
Yeah, adopting Spring support is unlikely to be much burden and seems well
worthwhile.
On Sat, Jun 1, 2019 at 1:48 AM Claude Brisson
wrote:
Hi.
We are aware of the situation, and we were more or less
Hi Brent,
Am 2019-06-01 um 02:32 schrieb Brent Putman:
Hello,
I represent the Shibboleth project (https://www.shibboleth.net/), a
widely-used open-source platform for federated authentication (SAML,
CAS, and soon OpenID Connect). We make heavy use of Velocity in our
codebase, as well as Spring
Am 2019-06-11 um 13:32 schrieb Claude Brisson:
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
Here is my vote, +1
Looking forward to switch stuff to 2.2 in Doxia
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Am 2020-02-02 um 07:14 schrieb Henning Schmiedehausen:
Hi Claude,
thank you so much for all the work that went into this RC. I will give you
a +0.5 (as there are already three +1, I don't want to hold up the release)
- builds and passes tests on MacOS running java 8 (OpenJDK 64-Bit Server VM
Am 2021-01-29 um 19:29 schrieb Claude Brisson:
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) :
Am 2021-03-01 um 21:26 schrieb Claude Brisson:
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
Am 2021-02-27 um 11:15 schrieb Claude Brisson:
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
Am 2022-11-09 um 09:39 schrieb Greg Huber:
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
Folks,
I'd like to integrate Velocity Tools 3.2 into next release of Maven
Doxia Sitetools, thus Maven Site Plugin. Is anyone willing to to do the
3.2 release?
Michael
-
To unsubscribe, e-mail:
Am 2023-03-14 um 01:15 schrieb Claude Brisson:
There is some work on the open issues... I'll try to get some done.
Merci, Claude !
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands,
Am 2023-03-25 um 12:59 schrieb Claude Brisson:
Hello.
Please vote for the release of the velocity-master release 5.
Changes:
+ upgraded parent apache pom to version 29
+ upgraded maven plugins to latest version
+ list Will Glass-Husain as Emeritus (I still wonder why we list the
staff in the
Am 2023-03-23 um 09:56 schrieb Claude Brisson:
On 22/03/2023 16:25, Michael Osipov wrote:
I wouldn't waste a single minute for that unless there is a strong
reason and user complaints. Only the servlet views and
request/session-related stuff is affected.
The engine is not affected
Am 2023-03-22 um 11:24 schrieb Claude Brisson:
And it should be better to first push out a release of the engine (there
is at least one CVE on the jdom dependency).
+1
Ah, and follow the movement and make the javax => jakarta migration,
shouldn't we? Then, how? Does it imply a major version
Claude,
the vote is over. Please proceed.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Claude,
is this still on your radar our should I use the current version during
the summer?
M
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Guys, last day for votes. Please have a look.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Guys, last day for votes. Please have a look.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Hi,
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12352138
Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1041/
Hi,
IMPORTANT: This requires the following staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1041/
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310130=12351146
Staging repo:
Am 2024-02-10 um 20:42 schrieb Michael Osipov:
Hi,
IMPORTANT: This requires the following staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1041/
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310130=12351146
Staging repo
Am 2024-02-10 um 20:33 schrieb Michael Osipov:
Hi,
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12352138
Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1041/
https://repository.apache.org/content/repositories
Canceling the vote and dropping the release. It did not reach the
required quorum.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
Canceling the vote and dropping the release. It did not reach the
required quorum.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On 2024/02/13 17:39:38 Claude Brisson wrote:
> Maybe it's nitpicking, but having the users being able to build without
> errors is a precaution which is worth repackaging an engine RC, since
> we're at it... no?
I don't consider this as nitpicking, but you need to consider the failure
reason
On 2024/02/13 15:23:36 Claude Brisson wrote:
> Ooops, changing my vote to -1, I have a problem building:
>
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 0.012 s <<< FAILURE! -- in
> org.apache.velocity.test.issues.VelTools66TestCase
> [ERROR]
>
On 2024/02/13 16:32:30 Michael Osipov wrote:
> On 2024/02/13 15:23:36 Claude Brisson wrote:
> > Ooops, changing my vote to -1, I have a problem building:
> >
> > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
&g
On 2024/02/13 15:25:42 Claude Brisson wrote:
> Since I could not build the engine RC, I cannot test the tools RC
> without tweaking the poms.
As a followup to your comments I found another issue for tests:
https://github.com/apache/velocity-tools/pull/17
Though, it is not a blocker because it
+1
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On 2024/02/19 20:25:45 Claude Brisson wrote:
> Version numbers are advertized and are supposed to be coherent. We don't
> care that the tags are public, they are not advertized. I didn't say
> that you had to reuse the tag. The tag can be named 2.4-RC2. You don't
> have to rename anything, or
On 2024/02/19 21:12:39 Claude Brisson wrote:
> On 19/02/2024 21:34, Michael Osipov wrote:
>
> > On 2024/02/19 20:25:45 Claude Brisson wrote:
> >> Version numbers are advertized and are supposed to be coherent. We don't
> >> care that the tags are public, they ar
Guys, please note that the vote ends today. If you intend to vote, vote today.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
On 2024/02/21 11:54:51 Claude Brisson wrote:
> > I use this one [1] sans the part which does not apply to Velocity TLP to
> > comply with ASF release requirements. If there is a documentation for the
> > Velocity project which does not have more manual steps compared to the [1],
> > I will
Canceling the vote and dropping the release. It did not reach the
required quorum.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
l or something like that, no? It's more annoying if
> there is a phantom 2.4 version number which has not been release, IMO.
>
> On 18/02/2024 13:45, Michael Osipov wrote:
> > Hi,
> >
> > Release notes:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?project
Folks,
Velocity Engine 2.4 has seven issues assigned [1]. I like to call the
vote for this version next week. I'll leave you at least week to raise
any concerns or to hold off the release if you want to add another issue
to the mix.
Meanwhile, please take a look at open PRs [2] and watch
Hi,
The vote has passed with the following result:
+1 (binding): Nathan Bubna, Claude Brisson, Michael Osipov
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
Hi,
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310104=12354231
Staging repo:
https://repository.apache.org/content/repositories/orgapachevelocity-1043/
On 2024/01/10 10:15:27 Gernot Hueller wrote:
>
> Hello all,
>
> VelocityTools (VelocityViewServlet and friends) reference Servlet API and
> that was stripped of any "Java" label not to violate Oracle's trademark
>
1 - 100 of 359 matches
Mail list logo
