You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by pa...@apache.org on 2026/08/18 08:29:43 UTC
(groovy-website) branch asf-site updated (78e674b -> 6f49928)
This is an automated email from the ASF dual-hosted git repository.
paulk-asert pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
from 78e674b Release 6.0.0-beta-2: update sitemap
new 84967c0 Groovy 6 release notes: align Grape Maven to Grape Ivy for checksum failure
new c81ddcf add links to Apache projects
new 6f49928 minor release note tweaks
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
site/src/site/blog/groovy-geaflow.adoc | 18 ++++++++++++------
site/src/site/releasenotes/groovy-6.0.adoc | 16 ++++++++++++++++
2 files changed, 28 insertions(+), 6 deletions(-)
(groovy-website) 03/03: minor release note tweaks
Posted by pa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
paulk-asert pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
commit 6f49928407fdd75f3f6b97898bc6c812bacbe44c
Author: Paul King <pa...@asert.com.au>
AuthorDate: Tue Aug 18 18:29:27 2026 +1000
minor release note tweaks
---
site/src/site/releasenotes/groovy-6.0.adoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/site/src/site/releasenotes/groovy-6.0.adoc b/site/src/site/releasenotes/groovy-6.0.adoc
index 849580c..df18530 100644
--- a/site/src/site/releasenotes/groovy-6.0.adoc
+++ b/site/src/site/releasenotes/groovy-6.0.adoc
@@ -3082,6 +3082,15 @@ engine's long-standing behaviour
Artifacts published without any checksum continue to resolve, as they do
with the Ivy engine, and `@GrabConfig(disableChecksums=true)` (or
`-Dgroovy.grape.disableChecksums`) still skips verification entirely.
+* A resolver root using a plaintext protocol, such as a `@GrabResolver`
+naming an `http://` repository, is now reported since artifacts fetched
+from it can be read or modified in transit
+(https://issues.apache.org/jira/browse/GROOVY-12266[GROOVY-12266]).
+`-Dgroovy.grape.insecureProtocolPolicy` selects `fail` to reject such a
+resolver, `warn` (the default) to log it and add the resolver anyway, or
+`ignore` to skip the check; roots naming a loopback host are exempt under
+every policy. The check applies to both engines, since every route to
+adding a resolver passes through the same facade.
[[platform-logging]]
== Platform Logging
(groovy-website) 02/03: add links to Apache projects
Posted by pa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
paulk-asert pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
commit c81ddcf8e4adb3ce3582f870ff3e00f4fc5cee84
Author: Paul King <pa...@asert.com.au>
AuthorDate: Tue Aug 18 18:29:04 2026 +1000
add links to Apache projects
---
site/src/site/blog/groovy-geaflow.adoc | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/site/src/site/blog/groovy-geaflow.adoc b/site/src/site/blog/groovy-geaflow.adoc
index 1c01815..a82f952 100644
--- a/site/src/site/blog/groovy-geaflow.adoc
+++ b/site/src/site/blog/groovy-geaflow.adoc
@@ -25,7 +25,8 @@ data warehouse acceleration. It was previously open-sourced under the name
_TuGraph Analytics_, as part of the same TuGraph family as the TuGraph
graph database we looked at in our earlier
https://groovy.apache.org/blog/groovy-graph-databases[Using Graph Databases with Groovy]
-post. GeaFlow entered the Apache Incubator in June 2025, and its
+post. GeaFlow entered the https://incubator.apache.org/[Apache Incubator]
+in June 2025, and its
first Apache releases are now available from Maven Central under the
`org.apache.geaflow` group id.
@@ -34,8 +35,9 @@ a graph _computing engine_ like GeaFlow focuses on running computations
over graphs: iterative algorithms like PageRank and shortest paths,
multi-hop traversals, and — GeaFlow's speciality — doing this
_incrementally over streaming data_, so that answers stay up-to-date
-as new vertices and edges arrive. If you know Apache Flink or
-Spark's GraphX, GeaFlow sits in a similar space, but with graphs
+as new vertices and edges arrive. If you know
+https://flink.apache.org/[Apache Flink] or
+https://spark.apache.org/[Spark]'s GraphX, GeaFlow sits in a similar space, but with graphs
as first-class citizens.
GeaFlow offers two programming interfaces:
@@ -335,8 +337,11 @@ FROM (
RETURN a.id as a_id, b.id as b_id, c.id as c_id, d.id as d_id, a.id as a1_id
);
----
-* *Connectors* for the DSL covering files, sockets, Kafka, Pulsar, Hive,
- JDBC, HBase, Elasticsearch, Hudi, Paimon, and even Neo4j.
+* *Connectors* for the DSL covering files, sockets,
+ https://kafka.apache.org/[Kafka], https://pulsar.apache.org/[Pulsar],
+ https://hive.apache.org/[Hive], JDBC, https://hbase.apache.org/[HBase],
+ Elasticsearch, https://hudi.apache.org/[Hudi],
+ https://paimon.apache.org/[Paimon], and even Neo4j.
* *Dynamic graph computation*: the same vertex-centric algorithms can
run incrementally against a graph view that is continuously updated
from streaming vertex and edge sources — GeaFlow's headline feature,
@@ -362,7 +367,8 @@ https://github.com/paulk-asert/groovy-geaflow
[NOTE]
====
Apache GeaFlow is an effort undergoing incubation at The Apache Software
-Foundation (ASF), sponsored by the Apache Incubator. Incubation is
+Foundation (ASF), sponsored by the Apache Incubator.
+https://incubator.apache.org/[Incubation] is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects.
(groovy-website) 01/03: Groovy 6 release notes: align Grape Maven to Grape Ivy for checksum failure
Posted by pa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
paulk-asert pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-website.git
commit 84967c05e9ca159ab0a300c4e07cea54f92089f8
Author: Paul King <pa...@asert.com.au>
AuthorDate: Tue Aug 18 12:11:08 2026 +1000
Groovy 6 release notes: align Grape Maven to Grape Ivy for checksum failure
---
site/src/site/releasenotes/groovy-6.0.adoc | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/site/src/site/releasenotes/groovy-6.0.adoc b/site/src/site/releasenotes/groovy-6.0.adoc
index 07578fb..849580c 100644
--- a/site/src/site/releasenotes/groovy-6.0.adoc
+++ b/site/src/site/releasenotes/groovy-6.0.adoc
@@ -3075,6 +3075,13 @@ bad JAR with a warning while the remaining artifacts continue to register.
POM-only stubs and corrupt artifacts so a poisoned cache entry is
re-fetched rather than silently used; a relaxed configuration is
available for environments that need the previous lenient behaviour.
+* A checksum mismatch now fails resolution in the Maven engine rather
+than logging a warning and using the artifact anyway, matching the Ivy
+engine's long-standing behaviour
+(https://issues.apache.org/jira/browse/GROOVY-12265[GROOVY-12265]).
+Artifacts published without any checksum continue to resolve, as they do
+with the Ivy engine, and `@GrabConfig(disableChecksums=true)` (or
+`-Dgroovy.grape.disableChecksums`) still skips verification entirely.
[[platform-logging]]
== Platform Logging