Merge branch '7.0.x' into 7.0.x-gson-datecal-precision

Author: codeconsole

.github/vote_templates/announce.txt

@@ -2,7 +2,7 @@ The Apache Grails community is pleased to announce the release of Apache Grails
 
 Grails is a powerful Groovy-based web application framework for the JVM built on top of Spring Boot that has many plugins to further extend its functionality.
 
-This release another milestone on our journey to a final 7.0 release. Users are encouraged to try the milestone to provide early feedback. Detailed upgrade instructions are available here: https://docs.grails.org/${VERSION}/guide/upgrading.html
+This release another milestone on our journey to a final 7.0 release. Users are encouraged to try the milestone to provide early feedback. Detailed upgrade instructions are available here: https://grails.apache.org/docs/${VERSION}/guide/upgrading.html
 
 The release notes are available here:
 <blog post link>

CONTRIBUTING.md

@@ -19,7 +19,7 @@ limitations under the License.
 
 First off, thanks for taking the time to contribute! ❤️
 
-Grails is an open source project with an active community and we rely heavily on that community to help make Grails better. As such, there are various ways in which people can contribute to Grails. One of these is by [writing useful plugins](https://docs.grails.org/latest/guide/plugins.html) and making them publicly available.
+Grails is an open source project with an active community and we rely heavily on that community to help make Grails better. As such, there are various ways in which people can contribute to Grails. One of these is by [writing useful plugins](https://grails.apache.org/docs/latest/guide/plugins.html) and making them publicly available.
 
 All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
 
@@ -49,7 +49,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 ## I Have a Question
 
-> If you want to ask a question, we assume that you have read the available [Documentation](https://docs.grails.org/latest/).
+> If you want to ask a question, we assume that you have read the available [Documentation](https://grails.apache.org/docs/latest/).
 
 Before you ask a question, it is best to search for existing [Issues](https://github.com/apache/grails-core/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
@@ -63,7 +63,7 @@ If you then still feel the need to ask a question and need clarification, we rec
 
 ## I Want to Write a Grails Plugin
 
-[Grails Plugins](https://docs.grails.org/latest/guide/plugins.html) are similar to a Grails Application project, but they include a plugin descriptor and package shared functionality for other Grails Applications to use.  More information can be found [here](https://docs.grails.org/latest/guide/plugins.html#creatingAndInstallingPlugins).
+[Grails Plugins](https://grails.apache.org/docs/latest/guide/plugins.html) are similar to a Grails Application project, but they include a plugin descriptor and package shared functionality for other Grails Applications to use.  More information can be found [here](https://grails.apache.org/docs/latest/guide/plugins.html#creatingAndInstallingPlugins).
 
 ## I Want to Contribute
 
@@ -79,7 +79,7 @@ If you then still feel the need to ask a question and need clarification, we rec
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
 
 - Make sure that you are using the latest version.
-- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://docs.grails.org/latest/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://grails.apache.org/docs/latest/). If you are looking for support, you might want to check [this section](#i-have-a-question)).
 - To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/apache/grails-coreissues?q=label%3Abug).
 - Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
 - Collect information about the bug:
@@ -116,7 +116,7 @@ This section guides you through submitting an enhancement suggestion for Grails,
 #### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
-- Read the [documentation](https://docs.grails.org/latest/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Read the [documentation](https://grails.apache.org/docs/latest/) carefully and find out if the functionality is already covered, maybe by an individual configuration.
 - Perform a [search](https://github.com/apache/grails-core/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
 
@@ -193,9 +193,9 @@ By default, Grails forks a JVM to run the application. The `-debug-jvm` argument
 
 ### Improving The Documentation
 
-There are many aspects to [Grail's documentation](https://docs.grails.org/)
-- [API](https://docs.grails.org/latest/api/) documentation in the code itself via javadoc & groovydoc.
-- [The Grails User Guide](https://docs.grails.org/latest/guide/single.html) from the `grails-doc` project in this
+There are many aspects to [Grail's documentation](https://grails.apache.org/docs/)
+- [API](https://grails.apache.org/docs/latest/api/) documentation in the code itself via javadoc & groovydoc.
+- [The Grails User Guide](https://grails.apache.org/docs/latest/guide/single.html) from the `grails-doc` project in this
   repository.
 - Various how-to [Guides](https://guides.grails.org/index.html) from
   the [grails-guides](https://github.com/grails-guides) Organization.

INSTALL

@@ -1,7 +1,7 @@
 Grails Installation Guide
 =======================
 
-Grails is a powerful Groovy-based web application framework for the JVM built on top of Spring Boot that has many plugins to further extend its functionality. The full documentation for how to install Grails via different mechanisms and use it can be found at `https://docs.grails.org/latest`.  This document specifically covers the basic building and installation of Grails from a source distribution.
+Grails is a powerful Groovy-based web application framework for the JVM built on top of Spring Boot that has many plugins to further extend its functionality. The full documentation for how to install Grails via different mechanisms and use it can be found at `https://grails.apache.org/docs/latest`.  This document specifically covers the basic building and installation of Grails from a source distribution.
 
 How to use the source distribution
 ------------------------------

README.md

@@ -16,7 +16,7 @@ limitations under the License.
 
 # Apache Grails
 
-[![Documentation](https://img.shields.io/badge/Documentation-595959)](https://docs.grails.org)
+[![Documentation](https://img.shields.io/badge/Documentation-595959)](https://grails.apache.org/docs/)
 [![Develocity](https://img.shields.io/badge/Develocity-06A0CE?logo=Gradle&labelColor=06A0CE)](https://ge.grails.org/scans)
 [![CI](https://github.com/apache/grails-core/actions/workflows/gradle.yml/badge.svg?event=push)](https://github.com/apache/grails-core/actions/workflows/gradle.yml)
 [![Groovy Joint Validation Build](https://github.com/apache/grails-core/actions/workflows/groovy-joint-workflow.yml/badge.svg?event=push)](https://github.com/apache/grails-core/actions/workflows/groovy-joint-workflow.yml)
@@ -38,7 +38,7 @@ Please see the [INSTALL](INSTALL) document for instructions on how to build, use
 
 ## Getting help
 
-- Check the [Documentation](https://docs.grails.org/) for your preferred Apache Grails version.
+- Check the [Documentation](https://grails.apache.org/docs/) for your preferred Apache Grails version.
 - Check for a [Grails Guide](https://github.com/grails-guides/).
 - Ask questions on the [Grails User Mailing List](https://lists.apache.org/[email protected])
 - Submit an issue: [Grails Issues](https://github.com/apache/grails-core/issues)
@@ -73,13 +73,13 @@ To create an Apache Grails Application with the wrapper follow these steps:
 3. Run the wrapper command `grailsw -t forge create-app` to create a new Apache Grails Application.
 
 Please note, that the wrapper supports either the legacy `Apache Grails Shell` or the newer `Apache Grails Forge` CLI.
-For more detailed information about it, see the [documentation](https://docs.grails.org/snapshot/index.html).
+For more detailed information about it, see the [documentation](https://grails.apache.org/docs/snapshot/index.html).
 
 #### Wrapper - Running Commands inside a Apache Grails Project
 
 For running commands, the Grails Wrapper will always pull the Apache Grails version from `gradle.properties` and ignore
 any environment variables. Type `grailsw -t shell help` to see the available commands. For more detailed information
-about it, see the [documentation](https://docs.grails.org/snapshot/index.html).
+about it, see the [documentation](https://grails.apache.org/docs/snapshot/index.html).
 
 ### grails-shell-cli
 
@@ -110,7 +110,7 @@ Once your Apache Grails Application is created, you can start it with the comman
 
     ./gradlew bootRun
 
-For further information, please consult the [documentation](https://docs.grails.org).
+For further information, please consult the [documentation](https://grails.apache.org/docs/).
 
 ## Licensing
 

grails-data-docs/guide-rx/src/main/docs/gettingStarted/CRUD.adoc

@@ -79,7 +79,7 @@ Book.get(id)
     }
 ----
 
-The `switchMap` transforms an `Observable` and converts the result into another `Observable`. However, this is not the most efficient way to perform updates as you can use https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#whereQueries[where queries] to update an instance without retrieving it:
+The `switchMap` transforms an `Observable` and converts the result into another `Observable`. However, this is not the most efficient way to perform updates as you can use https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#whereQueries[where queries] to update an instance without retrieving it:
 
 
 [source,groovy]

grails-data-docs/guide-rx/src/main/docs/gettingStarted/creatingDomainClasses.adoc

@@ -44,4 +44,4 @@ NOTE: The type is provided as a generic argument to the `RxMongoEntity` trait. T
 
 In addition, for MongoDB an `id` of type `ObjectId` is required.
 
-For more information on domain modelling in GORM, take a look at the https://docs.grails.org/latest/guide/GORM.html#domainClasses[GORM user guide] on the subject.
+For more information on domain modelling in GORM, take a look at the https://grails.apache.org/docs/latest/guide/GORM.html#domainClasses[GORM user guide] on the subject.

grails-data-docs/guide-rx/src/main/docs/introduction.adoc

@@ -19,7 +19,7 @@ under the License.
 
 == Introduction
 
-https://docs.grails.org/lastest/grails-data/[GORM], the object mapping technology built into the Grails framework, has traditionally been a primarily blocking API.
+https://grails.apache.org/docs/lastest/grails-data/[GORM], the object mapping technology built into the Grails framework, has traditionally been a primarily blocking API.
 
 Async features were added in GORM 4, however these are merely a way to isolate your blocking operations onto a different thread and not a truly non-blocking implementation.
 

grails-data-docs/guide-rx/src/main/docs/querying/dynamicFinders.adoc

@@ -18,7 +18,7 @@ under the License.
 ////
 
 === Dynamic Finders
-Although _Where queries_ are preferred, _Dynamic finders_ are another option for simple queries and are also very expressive. The https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#finders[syntax for Dynamic finders is described in the GORM user guide]. The major difference in RxGORM is that all dynamic finders return an `rx.Observable`:
+Although _Where queries_ are preferred, _Dynamic finders_ are another option for simple queries and are also very expressive. The https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#finders[syntax for Dynamic finders is described in the GORM user guide]. The major difference in RxGORM is that all dynamic finders return an `rx.Observable`:
 
 [source,groovy]
 ----

grails-data-docs/guide-rx/src/main/docs/querying/index.adoc

@@ -20,10 +20,10 @@ under the License.
 == Querying
 RxGORM supports all the typical ways of querying that you are used to with GORM including:
 
-* https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#finders[Dynamic finders]
-* https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#whereQueries[Where queries]
-* https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#detachedCriteria[Detached Criteria]
-* https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#criteria[Criteria queries]
+* https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#finders[Dynamic finders]
+* https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#whereQueries[Where queries]
+* https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#detachedCriteria[Detached Criteria]
+* https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#criteria[Criteria queries]
 
 The major difference is that all query operations return an `Observable`. In this section we will go through the various ways you can query for GORM objects.
 

grails-data-docs/guide-rx/src/main/docs/querying/whereQueries.adoc

@@ -56,4 +56,4 @@ Book.where { title == 'The Stand' }
     }
 ----
 
-For more information on the syntax of where queries see the https://docs.grails.org/latest/grails-data/hibernate5/manual/index.html#whereQueries[relevant section in the GORM documentation].
+For more information on the syntax of where queries see the https://grails.apache.org/docs/latest/grails-data/hibernate5/manual/index.html#whereQueries[relevant section in the GORM documentation].