This is an automated email from the ASF dual-hosted git repository.

asf-ci-deploy pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/grails-doc.git


The following commit(s) were added to refs/heads/gh-pages by this push:
     new d5f6d3a4e4 Deploying to documentation branch - 19:44:55
d5f6d3a4e4 is described below

commit d5f6d3a4e460ca332a3235eb8e6daf93bb63dcac
Author: jdaugherty <[email protected]>
AuthorDate: Thu Sep 18 19:44:56 2025 +0000

    Deploying to documentation branch - 19:44:55
---
 snapshot/guide/pages/upgrading60x.html | 13 +++++++++++--
 snapshot/guide/single.html             | 13 +++++++++++--
 snapshot/guide/upgrading.html          | 13 +++++++++++--
 3 files changed, 33 insertions(+), 6 deletions(-)

diff --git a/snapshot/guide/pages/upgrading60x.html 
b/snapshot/guide/pages/upgrading60x.html
index 34bcee4975..099f2e14ed 100644
--- a/snapshot/guide/pages/upgrading60x.html
+++ b/snapshot/guide/pages/upgrading60x.html
@@ -183,8 +183,8 @@ Doing so will ensure a seamless transition to the latest 
version of Grails and e
 <h4 id="_2_groovy_4_0_28_as_a_baseline">2. Groovy 4.0.28 as a baseline:</h4>
 <div class="paragraph">
 <p>Grails 7.0.0-SNAPSHOT adopts Groovy 4.0.28 as it&#8217;s baseline 
requirement.
-Several changes in Groovy 4 can affect your application.
-Notable changes include:</p>
+Several changes in <a 
href="https://groovy-lang.org/releasenotes/groovy-4.0.html";>Groovy 4</a> can 
affect your application.
+Changes that may affect a Grails Application or Plugin include:</p>
 </div>
 <div class="olist arabic">
 <ol class="arabic">
@@ -197,6 +197,15 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p><a href="https://issues.apache.org/jira/browse/GROOVY-5169";>GROOVY-5169</a> 
&amp; <a 
href="https://issues.apache.org/jira/browse/GROOVY-10449";>GROOVY-10449</a> - 
Fields with a public modifier were not returned with 
MetaClassImpl#getProperties() in groovy 3, but are now.</p>
 </li>
+<li>
+<p>Closures using the DELEGATE_FIRST strategy now behave differently.
+The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
+In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+</li>
+<li>
+<p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.
+See <a 
href="https://issues.apache.org/jira/browse/GROOVY-11568";>GROOVY-11568</a> for 
more details.</p>
+</li>
 </ol>
 </div>
 <div class="paragraph">
diff --git a/snapshot/guide/single.html b/snapshot/guide/single.html
index 695b33d678..5af0593402 100644
--- a/snapshot/guide/single.html
+++ b/snapshot/guide/single.html
@@ -2356,8 +2356,8 @@ Doing so will ensure a seamless transition to the latest 
version of Grails and e
 <h4 id="_2_groovy_4_0_28_as_a_baseline">2. Groovy 4.0.28 as a baseline:</h4>
 <div class="paragraph">
 <p>Grails 7.0.0-SNAPSHOT adopts Groovy 4.0.28 as it&#8217;s baseline 
requirement.
-Several changes in Groovy 4 can affect your application.
-Notable changes include:</p>
+Several changes in <a 
href="https://groovy-lang.org/releasenotes/groovy-4.0.html";>Groovy 4</a> can 
affect your application.
+Changes that may affect a Grails Application or Plugin include:</p>
 </div>
 <div class="olist arabic">
 <ol class="arabic">
@@ -2370,6 +2370,15 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p><a href="https://issues.apache.org/jira/browse/GROOVY-5169";>GROOVY-5169</a> 
&amp; <a 
href="https://issues.apache.org/jira/browse/GROOVY-10449";>GROOVY-10449</a> - 
Fields with a public modifier were not returned with 
MetaClassImpl#getProperties() in groovy 3, but are now.</p>
 </li>
+<li>
+<p>Closures using the DELEGATE_FIRST strategy now behave differently.
+The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
+In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+</li>
+<li>
+<p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.
+See <a 
href="https://issues.apache.org/jira/browse/GROOVY-11568";>GROOVY-11568</a> for 
more details.</p>
+</li>
 </ol>
 </div>
 <div class="paragraph">
diff --git a/snapshot/guide/upgrading.html b/snapshot/guide/upgrading.html
index a42838c2f3..7b5e82bcd6 100644
--- a/snapshot/guide/upgrading.html
+++ b/snapshot/guide/upgrading.html
@@ -212,8 +212,8 @@ Doing so will ensure a seamless transition to the latest 
version of Grails and e
 <h4 id="_2_groovy_4_0_28_as_a_baseline">2. Groovy 4.0.28 as a baseline:</h4>
 <div class="paragraph">
 <p>Grails 7.0.0-SNAPSHOT adopts Groovy 4.0.28 as it&#8217;s baseline 
requirement.
-Several changes in Groovy 4 can affect your application.
-Notable changes include:</p>
+Several changes in <a 
href="https://groovy-lang.org/releasenotes/groovy-4.0.html";>Groovy 4</a> can 
affect your application.
+Changes that may affect a Grails Application or Plugin include:</p>
 </div>
 <div class="olist arabic">
 <ol class="arabic">
@@ -226,6 +226,15 @@ It is advisable to switch to the new form of the 
property.</p>
 <li>
 <p><a href="https://issues.apache.org/jira/browse/GROOVY-5169";>GROOVY-5169</a> 
&amp; <a 
href="https://issues.apache.org/jira/browse/GROOVY-10449";>GROOVY-10449</a> - 
Fields with a public modifier were not returned with 
MetaClassImpl#getProperties() in groovy 3, but are now.</p>
 </li>
+<li>
+<p>Closures using the DELEGATE_FIRST strategy now behave differently.
+The resolution order in Groovy 3 used to be Delegate&#8217;s invokeMethod, 
Owner&#8217;s invokeMethod, Delegate&#8217;s invokeMissingMethod, Owner&#8217;s 
invokeMissingMethod.
+In Groovy 4, the order iw now Delegate&#8217;s invokeMethod, Delegate&#8217;s 
invokeMissingMethod, Owner&#8217;s invokeMethod, Owner&#8217;s 
invokeMissingMethod.</p>
+</li>
+<li>
+<p>Closures defined in a parent class that reference its private properties or 
methods may no longer have access to them in subclasses.
+See <a 
href="https://issues.apache.org/jira/browse/GROOVY-11568";>GROOVY-11568</a> for 
more details.</p>
+</li>
 </ol>
 </div>
 <div class="paragraph">

Reply via email to