Author: maartenc
Date: Sun Jan 5 10:51:22 2025
New Revision: 1922898
URL: http://svn.apache.org/viewvc?rev=1922898&view=rev
Log:
Updated KEYS URL
Modified:
ant/site/ivy/production/download.html
ant/site/ivy/sources/download.html
Modified: ant/site/ivy/production/download.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/download.html?rev=1922898&r1=1922897&r2=1922898&view=diff
==============================================================================
--- ant/site/ivy/production/download.html (original)
+++ ant/site/ivy/production/download.html Sun Jan 5 10:51:22 2025
@@ -198,7 +198,7 @@ ant jar
</pre>
Then you will find ivy.jar in <b>build/artifact</b>.<br class="xooki-br"/><br
class="xooki-br"/><h2>Snapshot build</h2>
The Apache Software Foundation hosts an installation of the Jenkins CI-system
where a continuous build of Ivy is available. Note that these are not official
builds and they are not endorsed or even supported by the Apache Ivy team. But
if you have problems with testing the latest (successful) build, you are
welcome to post that on the mailinglist. <br class="xooki-br"/><br
class="xooki-br"/>The project page of Apache Ivy on this Jenkins installation
is: <a
href="https://builds.apache.org/job/Ivy/";>https://builds.apache.org/job/Ivy/</a>.
Here you can find links to the latest version of the jars.<br
class="xooki-br"/><br class="xooki-br"/><h2><a name="VerifyReleases">Verify
Releases</a></h2>
-It is essential that you verify the integrity of the downloaded files using
the PGP signature or the SHA512 checksum. The checksums are not as strong
indicators as the PGP signature.<br class="xooki-br"/><br class="xooki-br"/>The
PGP signatures can be verified using PGP or GPG. First download the <a
href="https://www.apache.org/dist/ant/KEYS";>KEYS</a> as well as the asc
signature file for the particular distribution. Make sure you get these files
from the <a href="https://downloads.apache.org/ant/ivy/";>main distribution
directory</a>, rather than from a mirror. Then verify the signatures using<br
class="xooki-br"/>
+It is essential that you verify the integrity of the downloaded files using
the PGP signature or the SHA512 checksum. The checksums are not as strong
indicators as the PGP signature.<br class="xooki-br"/><br class="xooki-br"/>The
PGP signatures can be verified using PGP or GPG. First download the <a
href="https://downloads.apache.org/ant/KEYS";>KEYS</a> as well as the asc
signature file for the particular distribution. Make sure you get these files
from the <a href="https://downloads.apache.org/ant/ivy/";>main distribution
directory</a>, rather than from a mirror. Then verify the signatures using<br
class="xooki-br"/>
<pre>
% pgpk -a KEYS<br class="xooki-br"/>% pgpv apache-ivy-2.5.3-bin.tar.gz.asc
</pre>
Modified: ant/site/ivy/sources/download.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/sources/download.html?rev=1922898&r1=1922897&r2=1922898&view=diff
==============================================================================
--- ant/site/ivy/sources/download.html (original)
+++ ant/site/ivy/sources/download.html Sun Jan 5 10:51:22 2025
@@ -90,7 +90,7 @@ The project page of Apache Ivy on this J
<h2><a name="VerifyReleases">Verify Releases</a></h2>
It is essential that you verify the integrity of the downloaded files using
the PGP signature or the SHA512 checksum. The checksums are not as strong
indicators as the PGP signature.
-The PGP signatures can be verified using PGP or GPG. First download the <a
href="https://www.apache.org/dist/ant/KEYS";>KEYS</a> as well as the asc
signature file for the particular distribution. Make sure you get these files
from the <a href="https://downloads.apache.org/ant/ivy/";>main distribution
directory</a>, rather than from a mirror. Then verify the signatures using
+The PGP signatures can be verified using PGP or GPG. First download the <a
href="https://downloads.apache.org/ant/KEYS";>KEYS</a> as well as the asc
signature file for the particular distribution. Make sure you get these files
from the <a href="https://downloads.apache.org/ant/ivy/";>main distribution
directory</a>, rather than from a mirror. Then verify the signatures using
<code>
% pgpk -a KEYS
