Hi,
I've never done this before, but it seems like we need maven-gpg-plugin for
it [1].
Algorithm configuration would look like this:
--digest-algo=SHA512
Maybe this will help.
[1]
http://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/sign-mojo.html
пн, 28 дек. 2020 г. в
Igniters,
I've been preparing the 3.0.0-alpha1 release and got confused about the
requirements for checksums in Maven deployments. The Apache instruction [1]
states that MD5 is deprecated and SHA1 should be avoided in favor of
SHA-256 or SHA-512. However, it looks like we are still using the
Valentin Kulichenko created IGNITE-13916:
Summary: POM structure is incorrect
Key: IGNITE-13916
URL: https://issues.apache.org/jira/browse/IGNITE-13916
Project: Ignite
Issue Type:
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Control Utility
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility?branch=%3Cdefault%3E
No changes in the build
