This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 2163c35 fix broken links
2163c35 is described below
commit 2163c35d79beec800b3643995d692212b685c77a
Author: Paul King <[email protected]>
AuthorDate: Thu Jan 30 18:08:19 2025 +1000
fix broken links
---
site/src/site/blog/encryption-and-decryption-with-groovy.adoc | 2 +-
site/src/site/wiki/GEP-12.adoc | 2 +-
site/src/site/wiki/groovy-release-discussion.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/site/src/site/blog/encryption-and-decryption-with-groovy.adoc
b/site/src/site/blog/encryption-and-decryption-with-groovy.adoc
index 863671c..7352975 100644
--- a/site/src/site/blog/encryption-and-decryption-with-groovy.adoc
+++ b/site/src/site/blog/encryption-and-decryption-with-groovy.adoc
@@ -26,7 +26,7 @@ First, the cipher factory:
var factory = { Cipher.getInstance('AES/CBC/PKCS5Padding') }
----
-For our cipher algorithm, we are using the Advanced Encryption Standard
(https://en.wikipedia.org/wiki/Advanced_Encryption_Standard[AES]) algorithm, in
Cipher Block Chaining
(https://www.highgo.ca/2019/08/08/the-difference-in-five-modes-in-the-aes-encryption-algorithm/[CBC])
mode, with
https://en.wikipedia.org/wiki/Padding_(cryptography)#PKCS#5_and_PKCS#7[PKCS5
padding]. We'll look at other options later.
+For our cipher algorithm, we are using the Advanced Encryption Standard
(https://en.wikipedia.org/wiki/Advanced_Encryption_Standard[AES]) algorithm, in
Cipher Block Chaining
(https://www.highgo.ca/2019/08/08/the-difference-in-five-modes-in-the-aes-encryption-algorithm/[CBC])
mode, with
https://en.wikipedia.org/wiki/Padding_%28cryptography%29#PKCS%235_and_PKCS%237[PKCS5
padding]. We'll look at other options later.
Next we generate our secret key. Our secret key is our password. Only someone
who has the password will be able to decrypt the encrypted message. We could
use any random bits for our key, but like passwords, we want to choose a strong
key rather than a weak one. Cryptographic libraries provide classes to generate
such keys. We just need to provide the key size. AES supports 128, 192 and
256-bit keys. We'll choose 192 here:
diff --git a/site/src/site/wiki/GEP-12.adoc b/site/src/site/wiki/GEP-12.adoc
index a65d417..531abd4 100644
--- a/site/src/site/wiki/GEP-12.adoc
+++ b/site/src/site/wiki/GEP-12.adoc
@@ -210,7 +210,7 @@ selection based on the type provided by the open block.
In later versions of Groovy the static type checker has to be improved to
refine method selection by the given type
signature through the open block or lambda. A SAM type is then a fitting type
for the coercion only if the provided
types and the target types in the SAM are matching by number and type itself.
A more detailed description can be
-found here: http://cr.openjdk.org/~dlsmith/jsr335-0.6.1/F.html
+found here: https://cr.openjdk.org/~dlsmith/jsr335/jsr335-0.6.2/F.html
== References and useful links
diff --git a/site/src/site/wiki/groovy-release-discussion.adoc
b/site/src/site/wiki/groovy-release-discussion.adoc
index ed5c4e0..a189738 100644
--- a/site/src/site/wiki/groovy-release-discussion.adoc
+++ b/site/src/site/wiki/groovy-release-discussion.adoc
@@ -45,7 +45,7 @@ But in addition to those benefits, it's the release process
itself which greatly
* several build plans are dedicated to builds and releases:
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_UploadSnapshots&guest=1[snapshot
upload] plan builds Groovy from sources and deploys the artifacts to the
http://oss.jfrog.org/oss-snapshot-local/org/codehaus/groovy/[OSS Artifactory
Snapshot Repository].
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_ReleasePlan&guest=1[release
plan] allows a release manager to release a new version of Groovy directly
from the CI server
-** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_GvmBroadcast[GVM
broadcast] plan allows us to announce a new release of Groovy to
http://gvmtool.net/[GVM] and its https://twitter.com/gvmtool[Twitter account]
directly from the CI server
+** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_GvmBroadcast[GVM
broadcast] plan allows us to announce a new release of Groovy to
\http://gvmtool.net/ (obsolete - now SDKMAN) and its
https://twitter.com/gvmtool[Twitter account] directly from the CI server
** the
http://ci.groovy-lang.org/viewType.html?buildTypeId=Groovy_BintrayIntegration_GvmMakeDefault[GVM
default] plan allows us to notify GVM that a specific Groovy version is the
new default version, directly from the CI server
The last two GVM plans are separated because they need to be triggered
manually, once we are ready to announce that a new Groovy version is out. Let's
now describe what the release plan does, so that we can imagine what
adaptations will be required to go the Apache Way.
