+1 from my side now, signature verifies successfully and contents of the
jar did not change except for a few tomcat API updates
On 28.10.24 13:43, Richard Zowalla wrote:
339F3B2F72129ABCA81D96DA91EA7956A2DAD9CE should be now available in the KEYS
file.
Am 28.10.2024 um 13:20 schrieb Markus Jung <ju...@apache.org>:
-1 for now
looks like the .jar is signed with a key not published on
https://dist.apache.org/repos/dist/release/tomee/KEYS (I have all of them
imported):
➜ gpg --verify jakartaee-api-10.0.jar.asc
gpg: assuming signed data in 'jakartaee-api-10.0.jar'
gpg: Signature made Mo 28 Okt 2024 09:23:31 CET
gpg: using RSA key 339F3B2F72129ABCA81D96DA91EA7956A2DAD9CE
gpg: Can't check signature: No public key
Thanks
Markus
On 28.10.24 09:30, Richard Zowalla wrote:
Hi all,
this is a vote for a GA release of our JakartaEE 10 API shade artifact.
This release has no significant change compared to M2 but it now contains the
required signature tests as part of the build process.
The signature tests are green, so all good.
###############
Maven Repo:
https://repository.apache.org/content/repositories/orgapachetomee-1230/
###############
Source:
https://dist.apache.org/repos/dist/dev/tomee/jakartaee-api-10.0/
###############
Tag:
https://github.com/apache/tomee-jakartaee-api/releases/tag/jakartaee-api-parent-10.0
0901f0cbd0be92749fefc13261d92ddac6e6a2b6
###############
Please VOTE
[+1] go ship it
[+0] meh, don't care
[-1] stop, there is a ${showstopper}
The VOTE is open for 72h or as long as needed.
Gruß
Richard
