Alas despite tweaking my maven settings the release plugin still did
fetch the wrong key, which must be configured somewhere as a default...
I guess it's a minor issue if the comment of the key is wrong as long as
the key is declared in KEYS, I won't restart the release process just
for that.
On 09/10/2024 18:18, Claude Brisson wrote:
Thanks for the feedback. My mistake, wrong default key... I added the
key to my commiter ID.
We shall release 2.4.1 pretty soon, I'll check to use the correct key.
Claude
On 08/10/2024 13:00, Piotr Żygieło wrote:
Velocity Engine 2.4 is available in a binary and a source
distribution [4].
https://velocity.apache.org/download.html#velocity24
https://velocity.apache.org/download.html#verifying-integrity-of-downloaded-files
1. The published KEYS file does not contain the key used to sign 2.4
release.
2. The key used for the 2.4 release has an uid with text 'key for
org.republicate.webapp-slf4j-logger release', which I believe is a
different project.
Could at least the key 52F136DD be added to KEYS, please?
Piotrek
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org
For additional commands, e-mail: user-h...@velocity.apache.org
