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:
> Yes, Greg. It's a "normal" behavior, we're trying to release
> velocity-master (it's just a parent pom gathering some infos),
> velocity-engine
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
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
Yes, Greg. It's a "normal" behavior, we're trying to release
velocity-master (it's just a parent pom gathering some infos),
velocity-engine and velocity-tools in the same process. So you *have* to
clone and install manually velocity-master-4 in your local repository
before trying to use 2.3,
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
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
