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 21e3d68  minor changes
21e3d68 is described below

commit 21e3d68a9f9d4cb00e853e5b2e7f59c35332af60
Author: Paul King <[email protected]>
AuthorDate: Sun Mar 29 20:30:57 2026 +1000

    minor changes
---
 site/src/site/releasenotes/groovy-6.0.adoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/site/src/site/releasenotes/groovy-6.0.adoc 
b/site/src/site/releasenotes/groovy-6.0.adoc
index 2bd23a7..f5bb519 100644
--- a/site/src/site/releasenotes/groovy-6.0.adoc
+++ b/site/src/site/releasenotes/groovy-6.0.adoc
@@ -336,6 +336,9 @@ for (int i in 1..4) {
 // Output (non-deterministic order): 1, 16, 9, 4
 ----
 
+When running on JDK 21+, `@Parallel` will use virtual threads
+for lightweight concurrency; on earlier JDKs it falls back to platform threads.
+
 NOTE: `@Parallel` is an incubating transform favoring simplicity.
 Production use should consider proper concurrency mechanisms.
 
@@ -356,6 +359,18 @@ same contract as existing class/method/field-level 
transforms.
 * Further subprojects, e.g. maybe GPars
 * async/await like functionality
 
+== Platform Logging
+
+Groovy 6 replaces direct `System.err` output with the JDK's
+Platform Logging API (`java.lang.System.Logger`)
+for internal errors and warnings
+(https://issues.apache.org/jira/browse/GROOVY-11886[GROOVY-11886]).
+This means Groovy's diagnostic messages can now be controlled
+through standard JVM logging configuration.
+By default, messages still appear on the console via `java.util.logging`,
+but users can plug in any logging framework (SLF4J, Log4j2, etc.)
+by providing a `System.LoggerFinder` implementation on the classpath.
+
 [[Groovy6.0-breaking]]
 == Breaking changes
 

Reply via email to