You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@grails.apache.org by gi...@apache.org on 2025/08/15 21:28:48 UTC
(grails-static-website) branch asf-site-production updated: Updating apache/grails-static-website asf-site-production branch for Github Actions run:16999719245
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site-production
in repository https://gitbox.apache.org/repos/asf/grails-static-website.git
The following commit(s) were added to refs/heads/asf-site-production by this push:
new 5a4176ccd3 Updating apache/grails-static-website asf-site-production branch for Github Actions run:16999719245
5a4176ccd3 is described below
commit 5a4176ccd3754e3013ca53c08c33770c070abcb6
Author: jamesfredley <ja...@users.noreply.github.com>
AuthorDate: Fri Aug 15 21:28:44 2025 +0000
Updating apache/grails-static-website asf-site-production branch for Github Actions run:16999719245
---
blog/2016-05-28.html | 2 +-
blog/2024-12-23-grails-7-m1.html | 2 +-
blog/2025-03-05-grails-7-m3.html | 2 +-
blog/2025-06-10-grails-7-m4.html | 4 ++--
blog/2025-07-15-grails-7-m5.html | 4 ++--
blog/2025-08-10-grails-7-rc1.html | 4 ++--
documentation.html | 12 +++---------
faq.html | 2 +-
foundation/minutes.xml | 2 +-
index.html | 4 ++--
profiles.html | 2 +-
rss.xml | 20 ++++++++++----------
12 files changed, 27 insertions(+), 33 deletions(-)
diff --git a/blog/2016-05-28.html b/blog/2016-05-28.html
index d0bcb8002e..98cabbd0b1 100644
--- a/blog/2016-05-28.html
+++ b/blog/2016-05-28.html
@@ -231,7 +231,7 @@
<p>Now that we have our backend largely ready to go, we’re ready to set up React.</p>
<blockquote>
<p>Question: Why Do This?</p>
-<p>Why not use separate backend and front-end apps? In a microservice architecture, the work we’ve done might be sufficient - we could now build a separate React/node-based front-end application independent of our Grails backend. This is a great strategy, and <a href="https://docs.grails.org/latest/guide/single.html#webApiAndAngularProfiles">Grails 3.1 ships with a profile</a> tailored to this use case (web-api). Another option is to take advantage of Gradle multi-project builds, with se [...]
+<p>Why not use separate backend and front-end apps? In a microservice architecture, the work we’ve done might be sufficient - we could now build a separate React/node-based front-end application independent of our Grails backend. This is a great strategy, and <a href="https://docs.grails.org/latest/guide/profiles.html#creatingProfiles">Grails 3.1 ships with a profile</a> tailored to this use case (web-api). Another option is to take advantage of Gradle multi-project builds, with separate [...]
<p>In this article, however, we’re considering the use of React as the “view” (the V in MVC) in a standard Grails application. And although we’re sharing a project directory, the React code and Grails artifacts are independent, and will communicate at runtime via our restful API just as if they were separate apps. The only thing tying these two apps together is the same Gradle build, which gives us the benefits described earlier in the article (in fact, it would be quite easy to split ou [...]
<p>There’s many situations where a team may want to bring React into a Grails application, and it can be done in a way that allows for full developer productivity for both Grails and Node/React developers. Read on to see how!</p>
</blockquote>
diff --git a/blog/2024-12-23-grails-7-m1.html b/blog/2024-12-23-grails-7-m1.html
index b21b2d2c86..c4cce22661 100644
--- a/blog/2024-12-23-grails-7-m1.html
+++ b/blog/2024-12-23-grails-7-m1.html
@@ -298,7 +298,7 @@ grailsGradlePluginVersion=7.0.0-M3
</code></pre>
</li>
<li>
-<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with the new version. See https://docs.grails.org/7.0.0-M1/guide/single.html#upgrading60x.</p>
+<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with the new version. See https://docs.grails.org/7.0.0-M1/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you have specific versions defined in your build configuration, you may need to manually update them to align with Grails 7.0.0-M1.</p>
diff --git a/blog/2025-03-05-grails-7-m3.html b/blog/2025-03-05-grails-7-m3.html
index 16082b46f5..dcd5391479 100644
--- a/blog/2025-03-05-grails-7-m3.html
+++ b/blog/2025-03-05-grails-7-m3.html
@@ -320,7 +320,7 @@ grailsGradlePluginVersion=7.0.0-M4
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. See https://docs.grails.org/7.0.0-M3/guide/single.html#upgrading60x.</p>
+the new version. See https://docs.grails.org/7.0.0-M3/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
diff --git a/blog/2025-06-10-grails-7-m4.html b/blog/2025-06-10-grails-7-m4.html
index 9e8955bee8..d3cc86a2d5 100644
--- a/blog/2025-06-10-grails-7-m4.html
+++ b/blog/2025-06-10-grails-7-m4.html
@@ -165,7 +165,7 @@ meaning anyone can view your information. Make sure your email client does not a
<li>Addition of NOTICE to Grails Source</li>
<li>Created https://repo.grails.org/grails/restricted/ to replace https://repo.grails.org/grails/core longer term. This virtual repo's scope is significantly reduced to help reduce the chance of using outdated libraries.</li>
</ul>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M4/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M4/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -215,7 +215,7 @@ groovy.version=4.0.27
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. See https://docs.grails.org/7.0.0-M4/guide/single.html#upgrading60x.</p>
+the new version. See https://docs.grails.org/7.0.0-M4/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
diff --git a/blog/2025-07-15-grails-7-m5.html b/blog/2025-07-15-grails-7-m5.html
index f6102031af..bf099ece51 100644
--- a/blog/2025-07-15-grails-7-m5.html
+++ b/blog/2025-07-15-grails-7-m5.html
@@ -147,7 +147,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
<li>#14316 Use local repo commands instead of the github api for Release Drop Down population by @JudeRV in #14834</li>
</ul>
<p>Full Changelog: <a href="https://github.com/apache/grails-core/compare/v7.0.0-M4...v7.0.0-M5">v7.0.0-M4...v7.0.0-M5</a></p>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M5/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M5/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -213,7 +213,7 @@ to set it up.</p>
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. <a href="https://docs.grails.org/7.0.0-M5/guide/single.html#upgrading60x">See Upgrade Guide</a></p>
+the new version. <a href="https://docs.grails.org/7.0.0-M5/guide/upgrading.html#upgrading60x">See Upgrade Guide</a></p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
diff --git a/blog/2025-08-10-grails-7-rc1.html b/blog/2025-08-10-grails-7-rc1.html
index 5698ea96b5..6d303c8a1e 100644
--- a/blog/2025-08-10-grails-7-rc1.html
+++ b/blog/2025-08-10-grails-7-rc1.html
@@ -142,7 +142,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
<li>fix: #13705 - revert changes to Metadata from micronaut removal @jdaugherty (#14897)</li>
</ul>
<p>Full Changelog: <a href="https://github.com/apache/grails-core/compare/v7.0.0-M5...v7.0.0-RC1">v7.0.0-M5...v7.0.0-RC1</a></p>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-RC1/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-RC1/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -207,7 +207,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. <a href="https://docs.grails.org/7.0.0-RC1/guide/single.html#upgrading60x">See Upgrade Guide</a></p>
+the new version. <a href="https://docs.grails.org/7.0.0-RC1/guide/upgrading.html#upgrading60x">See Upgrade Guide</a></p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
diff --git a/documentation.html b/documentation.html
index 11a7a46e81..f6cbafd2f8 100644
--- a/documentation.html
+++ b/documentation.html
@@ -94,9 +94,6 @@
<h2>Latest Version (7.0.0-RC1) Documentation</h2>
</div>
<ul>
- <li>
- <a href='https://docs.grails.org/7.0.0-RC1/guide/single.html'>Single Page - User Guide</a>
- </li>
<li>
<a href='https://docs.grails.org/7.0.0-RC1/'>User Guide</a>
</li>
@@ -111,10 +108,10 @@
</div>
<ul>
<li>
- <a href='https://docs.grails.org/snapshot/guide/single.html'>Single Page - User Guide</a>
+ <a href='https://docs.grails.org/snapshot/'>User Guide</a>
</li>
<li>
- <a href='https://docs.grails.org/snapshot/'>User Guide</a>
+ <a href='https://docs.grails.org/snapshot/api/'>API Reference</a>
</li>
</ul>
</div><div class='guidegroup'>
@@ -177,9 +174,6 @@
<h2>Latest Version (6.2.3) Documentation</h2>
</div>
<ul>
- <li>
- <a href='https://docs.grails.org/6.2.3/guide/single.html'>Single Page - User Guide</a>
- </li>
<li>
<a href='https://docs.grails.org/6.2.3/'>User Guide</a>
</li>
@@ -193,7 +187,7 @@
<p>Browse previous versions' documentation since Grails 1.2.0</p>
<div class='versionselector'>
<h4>Single Page - User Guide</h4>
- <select onchange='window.location.href='https://docs.grails.org/' + this.value + '/guide/single.html''>
+ <select onchange='window.location.href='https://docs.grails.org/' + this.value + '/''>
<option>Select a version</option><option>6.2.3</option> <option>6.2.2</option> <option>6.2.1</option> <option>6.2.0</option> <option>6.2.0</option> <option>6.1.2</option> <option>6.1.2</option> <option>6.1.1</option> <option>6.1.1</option> <option>6.1.0</option> <option>6.0.0</option> <option>5.3.6</option> <option>5.3.5</option> <option>5.3.4</option> <option>5.3.3</option> <option>5.3.2</option> <option>5.3.1</option> <option>5.3.0</option> <option>5.2.6</option> <option>5. [...]
</select>
</div>
diff --git a/faq.html b/faq.html
index 15865332db..c747f18eb7 100644
--- a/faq.html
+++ b/faq.html
@@ -129,7 +129,7 @@
</div>
<div class='question' id='question_docs'>
- <h2 class='columnheader'>How can I contribute to improving the documentation?</h2><p>Grails documentation comes in several forms:<br/>- the <a href="https://docs.grails.org/latest/guide/single.html">reference documentation</a> contains language specification, user guides, a getting started tutorial, and more.<br/>- the <a href="api.html">GroovyDoc APIs</a> documents the classes of the Grails code base<br/>- <a href="https://github.com/apache/grails-static-website">GitHub</a> allows [...]
+ <h2 class='columnheader'>How can I contribute to improving the documentation?</h2><p>Grails documentation comes in several forms:<br/>- the <a href="https://docs.grails.org/latest/">reference documentation</a> contains language specification, user guides, a getting started tutorial, and more.<br/>- the <a href="api.html">GroovyDoc APIs</a> documents the classes of the Grails code base<br/>- <a href="https://github.com/apache/grails-static-website">GitHub</a> allows users to contrib [...]
</div>
<div class='question' id='question_code'>
diff --git a/foundation/minutes.xml b/foundation/minutes.xml
index 7196667377..ad709d437b 100644
--- a/foundation/minutes.xml
+++ b/foundation/minutes.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0"><channel><title>Foundation | Grails Framework</title><link>https://grails.apache.org</link><description>A powerful Groovy-based web application framework for the JVM built on top of Spring Boot</description><pubDate>Fri, 15 Aug 2025 20:46:00 GMT</pubDate><item><title>Technology Advisory Board Meeting</title><link>https://grails.apache.org/foundation/minutes/20221128-tab.html< [...]
+<?xml version="1.0" encoding="UTF-8"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0"><channel><title>Foundation | Grails Framework</title><link>https://grails.apache.org</link><description>A powerful Groovy-based web application framework for the JVM built on top of Spring Boot</description><pubDate>Fri, 15 Aug 2025 21:26:50 GMT</pubDate><item><title>Technology Advisory Board Meeting</title><link>https://grails.apache.org/foundation/minutes/20221128-tab.html< [...]
<h3>Meeting Attendance:</h3>
<ul>
<li><strong>Puneet Behl</strong> - Grails Product Development Lead at Object Computing</li>
diff --git a/index.html b/index.html
index e49aa0abe0..99deeb221e 100644
--- a/index.html
+++ b/index.html
@@ -97,13 +97,13 @@
<div class="calltoaction">
<b>Read the docs</b>
<h2>
- <a href="https://docs.grails.org/7.0.0-RC1/guide/single.html">Documentation
+ <a href="https://docs.grails.org/7.0.0-RC1/">Documentation
<span class="version">7.0.0-RC1</span>
</a>
</h2>
<br>
<h2>
- <a href="https://docs.grails.org/6.2.3/guide/single.html">Documentation
+ <a href="https://docs.grails.org/6.2.3/">Documentation
<span class="version">6.2.3</span>
</a>
</h2>
diff --git a/profiles.html b/profiles.html
index a68d14f9b4..88a924874e 100644
--- a/profiles.html
+++ b/profiles.html
@@ -144,7 +144,7 @@
<h2>Third-Party Profiles</h2>
</div>
<ul>
- <li class='legend'>Use the following documentation to learn how to <a href="https://docs.grails.org/latest/guide/single.html#creatingProfiles">create your own application profiles</a>
+ <li class='legend'>Use the following documentation to learn how to <a href="https://docs.grails.org/latest/guide/profiles.html#creatingProfiles">create your own application profiles</a>
</li>
<li>
<a href='https://github.com/macprzepiora/web-vaadin8'>Vaadin</a>
diff --git a/rss.xml b/rss.xml
index fd5a6cb668..d3cd344155 100644
--- a/rss.xml
+++ b/rss.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0"><channel><title>Blog | Grails Framework</title><link>https://grails.apache.org</link><description>A powerful Groovy-based web application framework for the JVM built on top of Spring Boot</description><pubDate>Fri, 15 Aug 2025 20:46:03 GMT</pubDate><item><title>Apache Grails (Incubating) [%version] - Release Announcement</title><link>https://grails.apache.org/blog/2025-08-10- [...]
+<?xml version="1.0" encoding="UTF-8"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0"><channel><title>Blog | Grails Framework</title><link>https://grails.apache.org</link><description>A powerful Groovy-based web application framework for the JVM built on top of Spring Boot</description><pubDate>Fri, 15 Aug 2025 21:26:53 GMT</pubDate><item><title>Apache Grails (Incubating) [%version] - Release Announcement</title><link>https://grails.apache.org/blog/2025-08-10- [...]
<p>The Apache Grails (incubating) community is excited to announce the Milestone 7.0.0-RC1 release of the Grails Framework! <br />
We encourage you to try this pre-release version and provide your feedback <a href="https://github.com/apache/grails-core/issues">here</a>.</p>
<h2>Download Source Code and Binary Distributions</h2>
@@ -49,7 +49,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
<li>fix: #13705 - revert changes to Metadata from micronaut removal @jdaugherty (#14897)</li>
</ul>
<p>Full Changelog: <a href="https://github.com/apache/grails-core/compare/v7.0.0-M5...v7.0.0-RC1">v7.0.0-M5...v7.0.0-RC1</a></p>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-RC1/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-RC1/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -114,7 +114,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. <a href="https://docs.grails.org/7.0.0-RC1/guide/single.html#upgrading60x">See Upgrade Guide</a></p>
+the new version. <a href="https://docs.grails.org/7.0.0-RC1/guide/upgrading.html#upgrading60x">See Upgrade Guide</a></p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
@@ -259,7 +259,7 @@ We encourage you to try this pre-release version and provide your feedback <a hr
<li>#14316 Use local repo commands instead of the github api for Release Drop Down population by @JudeRV in #14834</li>
</ul>
<p>Full Changelog: <a href="https://github.com/apache/grails-core/compare/v7.0.0-M4...v7.0.0-M5">v7.0.0-M4...v7.0.0-M5</a></p>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M5/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M5/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -325,7 +325,7 @@ to set it up.</p>
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. <a href="https://docs.grails.org/7.0.0-M5/guide/single.html#upgrading60x">See Upgrade Guide</a></p>
+the new version. <a href="https://docs.grails.org/7.0.0-M5/guide/upgrading.html#upgrading60x">See Upgrade Guide</a></p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
@@ -485,7 +485,7 @@ meaning anyone can view your information. Make sure your email client does not a
<li>Addition of NOTICE to Grails Source</li>
<li>Created https://repo.grails.org/grails/restricted/ to replace https://repo.grails.org/grails/core longer term. This virtual repo's scope is significantly reduced to help reduce the chance of using outdated libraries.</li>
</ul>
-<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M4/guide/single.html#upgrading60x">documentation</a>.</p>
+<p>Upgrade instructions are available in the <a href="https://docs.grails.org/7.0.0-M4/guide/upgrading.html#upgrading60x">documentation</a>.</p>
<h2>Dependency Upgrades</h2>
<p>In this release, we've upgraded several dependency versions, including but not limited to the following:</p>
<ul>
@@ -535,7 +535,7 @@ groovy.version=4.0.27
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. See https://docs.grails.org/7.0.0-M4/guide/single.html#upgrading60x.</p>
+the new version. See https://docs.grails.org/7.0.0-M4/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
@@ -817,7 +817,7 @@ grailsGradlePluginVersion=7.0.0-M4
</li>
<li>
<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with
-the new version. See https://docs.grails.org/7.0.0-M3/guide/single.html#upgrading60x.</p>
+the new version. See https://docs.grails.org/7.0.0-M3/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you
@@ -1166,7 +1166,7 @@ grailsGradlePluginVersion=7.0.0-M3
</code></pre>
</li>
<li>
-<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with the new version. See https://docs.grails.org/7.0.0-M1/guide/single.html#upgrading60x.</p>
+<p>Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with the new version. See https://docs.grails.org/7.0.0-M1/guide/upgrading.html#upgrading60x.</p>
</li>
</ol>
<p>Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you have specific versions defined in your build configuration, you may need to manually update them to align with Grails 7.0.0-M1.</p>
@@ -6431,7 +6431,7 @@ class SkillsTestController {
<p>Now that we have our backend largely ready to go, we’re ready to set up React.</p>
<blockquote>
<p>Question: Why Do This?</p>
-<p>Why not use separate backend and front-end apps? In a microservice architecture, the work we’ve done might be sufficient - we could now build a separate React/node-based front-end application independent of our Grails backend. This is a great strategy, and <a href="https://docs.grails.org/latest/guide/single.html#webApiAndAngularProfiles">Grails 3.1 ships with a profile</a> tailored to this use case (web-api). Another option is to take advantage of Gradle multi-project builds, with se [...]
+<p>Why not use separate backend and front-end apps? In a microservice architecture, the work we’ve done might be sufficient - we could now build a separate React/node-based front-end application independent of our Grails backend. This is a great strategy, and <a href="https://docs.grails.org/latest/guide/profiles.html#creatingProfiles">Grails 3.1 ships with a profile</a> tailored to this use case (web-api). Another option is to take advantage of Gradle multi-project builds, with separate [...]
<p>In this article, however, we’re considering the use of React as the “view” (the V in MVC) in a standard Grails application. And although we’re sharing a project directory, the React code and Grails artifacts are independent, and will communicate at runtime via our restful API just as if they were separate apps. The only thing tying these two apps together is the same Gradle build, which gives us the benefits described earlier in the article (in fact, it would be quite easy to split ou [...]
<p>There’s many situations where a team may want to bring React into a Grails application, and it can be done in a way that allows for full developer productivity for both Grails and Node/React developers. Read on to see how!</p>
</blockquote>