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
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
Michael Osipov created VELTOOLS-206:
---
Summary: Upgrade to Velocity Engine 2.4.1
Key: VELTOOLS-206
URL: https://issues.apache.org/jira/browse/VELTOOLS-206
Project: Velocity Tools
Issue
michael-o opened a new pull request, #18:
URL: https://github.com/apache/velocity-tools/pull/18
There is no reason to duplicate information from the POM and force devs to
keep the information in sync.
--
This is an automated message from the Apache Git Service.
To respond to the message,
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
michael-o opened a new pull request, #17:
URL: https://github.com/apache/velocity-tools/pull/17
This fixes test failures on newer Java versions
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
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?
On 13/02/2024 18:09, Michael Osipov wrote:
On 2024/02/13 15:25:42 Claude Brisson wrote:
Since I could not build the engine RC, I
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]
org.apache.velocity.test.issues.VelTools66TestCase.testVelTools66 --
Time
It's too bad I'm so busy those days to incorporate a few more issues.
But +1 anyway, that's already something.
Claude
On 13/02/2024 14:35, Michael Osipov wrote:
Guys, last day for votes. Please have a look.
-
To
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:
> > 0.012 s <<< FAILURE! -- in
> >
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
Since I could not build the engine RC, I cannot test the tools RC
without tweaking the poms.
Usually, I first release the engine then the tools.
Also, I think it is a good practice to name RC tags 2.4-rc1, etc. and to
only tag the release with 2.4.
Best,
Claude
On 13/02/2024 14:35,
15 matches
Mail list logo
