You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@grails.apache.org by ja...@apache.org on 2026/05/03 23:31:04 UTC
(grails-static-website) 01/01: Replace legacy *.grails.org URLs with their canonical grails.apache.org targets
This is an automated email from the ASF dual-hosted git repository.
jamesfredley pushed a commit to branch fix-redirect-links
in repository https://gitbox.apache.org/repos/asf/grails-static-website.git
commit 63786e5370061005ef11f2e80e401fcd9d56b1bd
Author: James Fredley <ja...@users.noreply.github.com>
AuthorDate: Sun May 3 19:30:49 2026 -0400
Replace legacy *.grails.org URLs with their canonical grails.apache.org targets
The Plugins link in the site header pointed at https://plugins.grails.org,
which is kept alive only as a meta-refresh redirect back to
https://grails.apache.org/plugins.html. Many other internal links in the
guides, blog posts, and shared chrome had the same shape - they targeted a
legacy *.grails.org host that exists today only to bounce visitors to the
canonical grails.apache.org URL. Each of those redirects costs the user
an extra hop, hurts SEO, and breaks if any of the legacy hosts ever go
away.
Replace each redirect-bound URL with its canonical destination so internal
links resolve directly:
- plugins.grails.org -> grails.apache.org/plugins.html (paths under
/plugin/<vendor>/<name> are 404, so they collapse to the landing page)
- guides.grails.org<path> -> grails.apache.org/guides<path> (path-preserving)
- docs.grails.org<path> -> grails.apache.org/docs<path> (path-preserving)
- views.grails.org<path> -> grails.apache.org/docs/latest/guide/theWebLayer.html#gson
- async.grails.org<path> -> grails.apache.org/docs/latest/guide/async.html
- testing.grails.org<path> -> grails.apache.org/docs/latest/guide/testing.html
- gsp.grails.org<path> -> grails.apache.org/docs/latest/guide/theWebLayer.html#gsp
(the four subdomains above all redirect to the same fixed anchor on the
canonical site - the legacy path component is dropped at redirect time
anyway, so we point straight at the anchor)
- grails.org/<X>.html -> grails.apache.org/<X>.html
- grails.org/learn.html -> grails.apache.org/learning.html (page renamed)
- grails.org/plugin/<X> -> grails.apache.org/plugins.html (legacy 404)
- grails.org/blog<path> -> grails.apache.org/blog<path>
- grails.org/ root and bare grails.org -> grails.apache.org/
Intentionally NOT touched:
- gorm.grails.org/* - some paths (notably /latest/neo4j/manual/...) have
no canonical replacement on grails.apache.org because GORM for Neo4j
has not been updated for Grails 7/8. The gorm.grails.org URL is still
the current canonical destination for those readers.
- start.grails.org, slack.grails.org, repo.grails.org,
prev-snapshot.grails.org - these are canonical hosts that serve content
directly (the Forge, the Slack signup, the JFrog Maven repo, and the
Grails 8 snapshot Forge).
- grails.org/buildstatus.html - redirects to a GitHub README, not back
to grails.apache.org, so it falls outside the redirect-back-to-here
scope of this change.
- buildSrc/src/test/resources/parity-baseline/ - golden HTML snapshot of
the legacy site, used by ParityCheckGuideTask as a regression-test
fixture; rewriting it would corrupt the source-of-truth the renderer
is diffed against.
- buildSrc/src/main/groovy/website/qa/AdHocFixtureDiff.groovy,
buildSrc/src/main/groovy/website/gradle/tasks/Generate{Redirects,
RedirectStubs}{Manifest,}Task.groovy, ParityCheckGuideTask.groovy, and
StructuralDiffGuidesTask.groovy - these intentionally reference
guides.grails.org as the LEGACY_BASE for the redirect-stub generator
and parity baseline.
- README.md and buildSrc/VENDOR.md - both document the migration itself,
so the legacy URLs need to remain readable.
- minutes/20210321-tab.md - frozen historical record from the TAB.
Verified locally with `./gradlew validateGuides -PvalidationMode=both`
(93 guides parsed, 0 errors) and `./gradlew build` (renderSite succeeds;
the rendered Plugins link in build/dist/index.html is now
https://grails.apache.org/plugins.html as expected).
Assisted-by: claude-code:claude-opus-4-7
---
buildSrc/src/main/template/style/guideItem.html | 2 +-
buildSrc/src/main/template/style/layout.html | 2 +-
buildSrc/src/main/template/style/menu.html | 2 +-
.../src/main/template/style/referenceItem.html | 2 +-
.../v3/guide/buildInfoPlugin.adoc | 2 +-
.../v3/guide/perEnvironmentConfig.adoc | 2 +-
.../v4/guide/buildInfoPlugin.adoc | 2 +-
.../v4/guide/perEnvironmentConfig.adoc | 2 +-
.../v4/guide/customizingApi.adoc | 2 +-
.../v4/guide/customizingApi.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/domainClass.adoc | 4 +-
.../v4/guide/domainClassTest.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/v1Controller.adoc | 4 +-
.../v4/guide/v1FunctionalTests.adoc | 2 +-
.../v4/guide/versioning.adoc | 2 +-
.../v4/guide/domainClass.adoc | 4 +-
.../v4/guide/domainClassTest.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/v1Controller.adoc | 4 +-
.../v4/guide/v1FunctionalTests.adoc | 2 +-
.../v4/guide/versioning.adoc | 2 +-
.../v4/guide/domainClass.adoc | 4 +-
.../v4/guide/domainClassTest.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/v1Controller.adoc | 4 +-
.../v4/guide/v1FunctionalTests.adoc | 2 +-
.../v4/guide/versioning.adoc | 2 +-
.../v3/guide/addCreateAndSaveActions.adoc | 2 +-
.../v3/guide/gettingStarted.adoc | 2 +-
.../v3/guide/whatAreCommandObjects.adoc | 2 +-
.../v4/guide/addCreateAndSaveActions.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/whatAreCommandObjects.adoc | 2 +-
guides/common/common-functionalTestsIntro.adoc | 2 +-
guides/common/common-installGrails5.adoc | 2 +-
guides/common/common-installingGrails-grails3.adoc | 2 +-
guides/common/common-installingGrails.adoc | 2 +-
guides/common/common-quoteTagLib.adoc | 2 +-
guides/common/common-tipScaffolding.adoc | 2 +-
.../v3/guide/applicationProfile.adoc | 6 +--
.../v3/guide/console.adoc | 4 +-
.../v3/guide/controllers.adoc | 4 +-
.../v3/guide/createApp.adoc | 2 +-
.../v3/guide/creatingDomainClass.adoc | 2 +-
.../v3/guide/deployment.adoc | 2 +-
.../v3/guide/gspLinks.adoc | 2 +-
.../v3/guide/respond.adoc | 2 +-
.../v3/guide/runningTheApp.adoc | 6 +--
.../v3/guide/services.adoc | 2 +-
.../v3/guide/staticScaffolding.adoc | 14 +++----
.../v3/guide/testing.adoc | 4 +-
.../v3/guide/urlMappings.adoc | 2 +-
.../v3/guide/views.adoc | 2 +-
.../v4/guide/applicationProfile.adoc | 6 +--
.../v4/guide/console.adoc | 4 +-
.../v4/guide/controllers.adoc | 4 +-
.../v4/guide/createApp.adoc | 2 +-
.../v4/guide/creatingDomainClass.adoc | 2 +-
.../v4/guide/deployment.adoc | 2 +-
.../v4/guide/gspLinks.adoc | 2 +-
.../v4/guide/respond.adoc | 2 +-
.../v4/guide/runningTheApp.adoc | 6 +--
.../v4/guide/staticScaffolding.adoc | 14 +++----
.../v4/guide/testing.adoc | 4 +-
.../v4/guide/urlMappings.adoc | 2 +-
.../v4/guide/views.adoc | 2 +-
.../v6/guide/applicationProfile.adoc | 6 +--
.../v6/guide/console.adoc | 4 +-
.../v6/guide/controllers.adoc | 4 +-
.../v6/guide/createApp.adoc | 2 +-
.../v6/guide/creatingDomainClass.adoc | 2 +-
.../v6/guide/deployment.adoc | 2 +-
.../v6/guide/gspLinks.adoc | 2 +-
.../v6/guide/respond.adoc | 2 +-
.../v6/guide/runningTheApp.adoc | 6 +--
.../v6/guide/staticScaffolding.adoc | 14 +++----
.../v6/guide/testing.adoc | 4 +-
.../v6/guide/urlMappings.adoc | 2 +-
.../v6/guide/views.adoc | 2 +-
.../v4/guide/conclusion.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 4 +-
guides/grails-async-promises/v3/guide/initial.adoc | 2 +-
.../v3/guide/writingTheApp.adoc | 2 +-
guides/grails-async-promises/v4/guide/initial.adoc | 2 +-
.../v4/guide/writingTheApp.adoc | 2 +-
.../v3/guide/writingTheApp/views.adoc | 2 +-
.../v4/guide/writingTheApp/views.adoc | 2 +-
guides/grails-codenarc/v4/guide/multiproject.adoc | 2 +-
.../v4/guide/writingTheApp/taglib.adoc | 2 +-
.../v6/guide/writingTheApp/taglib.adoc | 2 +-
.../v3/guide/writingTheApp/taglib.adoc | 2 +-
.../v4/guide/writingTheApp/taglib.adoc | 2 +-
.../v3/guide/domainClassAndScaffold.adoc | 2 +-
.../v3/guide/unitTestSave.adoc | 2 +-
.../v4/guide/domainClassAndScaffold.adoc | 2 +-
.../v4/guide/unitTestSave.adoc | 2 +-
.../v3/guide/controller.adoc | 2 +-
.../v3/guide/security.adoc | 2 +-
.../v3/guide/writingTheApp.adoc | 2 +-
.../v4/guide/controller.adoc | 2 +-
.../v4/guide/security.adoc | 2 +-
.../v4/guide/writingTheApp.adoc | 2 +-
.../v3/guide/configuration.adoc | 2 +-
.../v3/guide/gettingStarted.adoc | 2 +-
.../v3/guide/gormevents.adoc | 2 +-
.../v3/guide/test.adoc | 2 +-
.../v3/guide/writingTheApp.adoc | 2 +-
.../v4/guide/configuration.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/gormevents.adoc | 2 +-
.../v4/guide/test.adoc | 2 +-
.../v4/guide/writingTheApp.adoc | 2 +-
.../v4/guide/nextSteps.adoc | 2 +-
.../v3/guide/writingTheApp/controller.adoc | 2 +-
.../v3/guide/writingTheApp/resources.adoc | 2 +-
.../writingTheApp/services/awsSesService.adoc | 2 +-
.../writingTheApp/services/sendGridService.adoc | 2 +-
.../v4/guide/writingTheApp/controller.adoc | 2 +-
.../v4/guide/writingTheApp/resources.adoc | 2 +-
.../writingTheApp/services/awsSesService.adoc | 2 +-
.../writingTheApp/services/sendGridService.adoc | 2 +-
guides/grails-events/v3/guide/gettingStarted.adoc | 2 +-
guides/grails-events/v3/guide/services.adoc | 2 +-
guides/grails-events/v3/guide/writingTheApp.adoc | 2 +-
guides/grails-events/v4/guide/gettingStarted.adoc | 2 +-
guides/grails-events/v4/guide/services.adoc | 2 +-
guides/grails-events/v4/guide/writingTheApp.adoc | 2 +-
.../v3/guide/writingTheApp/controller.adoc | 2 +-
.../v4/guide/writingTheApp/controller.adoc | 2 +-
.../v3/guide/unitTest.adoc | 2 +-
.../v4/guide/unitTest.adoc | 2 +-
.../grails-javamelody/v4/guide/gettingStarted.adoc | 2 +-
.../grails-logicaldelete/v3/guide/conclusion.adoc | 2 +-
.../v3/guide/gettingStarted.adoc | 2 +-
.../v3/guide/runningTheApp.adoc | 2 +-
.../grails-logicaldelete/v4/guide/conclusion.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/runningTheApp.adoc | 2 +-
guides/grails-micronaut-http/v5/guide/test.adoc | 2 +-
.../v4/guide/originalAppGrails.adoc | 2 +-
guides/grails-multi-datasource/v3/guide/views.adoc | 2 +-
guides/grails-multi-datasource/v4/guide/views.adoc | 2 +-
.../v4/guide/featuresgradlefiles.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/wheretoGoFromHere.adoc | 2 +-
.../v4/guide/bookApplicationRabbit.adoc | 2 +-
.../grails-rabbitmq/v4/guide/gettingStarted.adoc | 2 +-
.../v4/guide/domainClass.adoc | 6 +--
.../v4/guide/enableCors.adoc | 2 +-
.../v4/guide/writingTheApp.adoc | 2 +-
guides/grails-soap/v3/guide/soapLibrary.adoc | 2 +-
guides/grails-soap/v3/guide/test.adoc | 2 +-
guides/grails-soap/v4/guide/soapLibrary.adoc | 2 +-
guides/grails-soap/v4/guide/test.adoc | 2 +-
.../v3/guide/domainClass.adoc | 2 +-
.../grails-taglib-wyswyg-trix/v3/guide/taglib.adoc | 2 +-
.../v4/guide/domainClass.adoc | 2 +-
.../grails-taglib-wyswyg-trix/v4/guide/taglib.adoc | 2 +-
.../v3/guide/domainClass.adoc | 48 +++++++++++-----------
.../v3/guide/unitTests.adoc | 6 +--
.../v4/guide/domainClass.adoc | 48 +++++++++++-----------
.../v4/guide/unitTests.adoc | 6 +--
.../v3/guide/apiController.adoc | 4 +-
.../grails-test-security/v3/guide/domainClass.adoc | 2 +-
.../v4/guide/apiController.adoc | 4 +-
.../grails-test-security/v4/guide/domainClass.adoc | 2 +-
.../grails-tvmlapp/v3/guide/controllerIndex.adoc | 6 +--
guides/grails-tvmlapp/v3/guide/controllerShow.adoc | 2 +-
guides/grails-tvmlapp/v3/guide/domainClass.adoc | 4 +-
.../v3/guide/internationalization.adoc | 2 +-
.../grails-tvmlapp/v4/guide/controllerIndex.adoc | 6 +--
guides/grails-tvmlapp/v4/guide/controllerShow.adoc | 2 +-
guides/grails-tvmlapp/v4/guide/domainClass.adoc | 4 +-
.../v4/guide/internationalization.adoc | 2 +-
.../v3/guide/featuredImageCommand.adoc | 2 +-
.../grails-upload-file/v3/guide/writingTheApp.adoc | 2 +-
.../v4/guide/featuredImageCommand.adoc | 2 +-
.../grails-upload-file/v4/guide/writingTheApp.adoc | 2 +-
.../grails-vs-nodejs/v4/guide/authentication.adoc | 2 +-
guides/grails-vs-nodejs/v4/guide/deployment.adoc | 2 +-
.../grails-vs-nodejs/v4/guide/flavorsByUser.adoc | 2 +-
guides/grails-vs-nodejs/v4/guide/gorm.adoc | 4 +-
guides/grails-vs-nodejs/v4/guide/grails.adoc | 2 +-
guides/grails-vs-nodejs/v4/guide/reactProfile.adoc | 4 +-
guides/grails-vs-nodejs/v4/guide/ssl.adoc | 2 +-
guides/grails-vs-nodejs/v4/guide/summary.adoc | 8 ++--
guides/grails-vs-nodejs/v4/guide/websockets.adoc | 4 +-
guides/grails_i18n/v3/guide/localeNavBar.adoc | 4 +-
guides/grails_i18n/v3/guide/writingTheApp.adoc | 2 +-
guides/grails_i18n/v4/guide/localeNavBar.adoc | 4 +-
guides/grails_i18n/v4/guide/writingTheApp.adoc | 2 +-
.../grails_url_mappings/v4/guide/conclusion.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
guides/grails_url_mappings/v4/guide/testing.adoc | 2 +-
.../grails_url_mappings/v4/guide/urlMappings.adoc | 2 +-
guides/neo4j-movies/v4/guide/byTitleEndpoint.adoc | 2 +-
.../v3/guide/specialForms/chainingDCAndNQ.adoc | 2 +-
.../guide/updatingTheService/queryParameters.adoc | 2 +-
.../v4/guide/specialForms/chainingDCAndNQ.adoc | 2 +-
.../guide/updatingTheService/queryParameters.adoc | 2 +-
guides/react-spring-security/v4/guide/server.adoc | 2 +-
guides/resources/style/menu.html | 2 +-
guides/resources/style/referenceItem.html | 2 +-
guides/rest-hibernate/v3/guide/controller.adoc | 2 +-
guides/rest-hibernate/v3/guide/gettingStarted.adoc | 2 +-
guides/rest-hibernate/v3/guide/json.adoc | 4 +-
guides/rest-hibernate/v4/guide/controller.adoc | 2 +-
guides/rest-hibernate/v4/guide/gettingStarted.adoc | 2 +-
guides/rest-hibernate/v4/guide/json.adoc | 4 +-
guides/rest-mongodb/v4/guide/applyConstraints.adoc | 4 +-
guides/rest-mongodb/v4/guide/controller.adoc | 2 +-
guides/rest-mongodb/v4/guide/gettingStarted.adoc | 2 +-
guides/rest-mongodb/v4/guide/json.adoc | 4 +-
guides/rest-mongodb/v4/guide/testing.adoc | 2 +-
.../server-sent-events/v3/guide/gradleConfig.adoc | 2 +-
.../server-sent-events/v4/guide/gradleConfig.adoc | 2 +-
.../v3/guide/buildingApi.adoc | 2 +-
.../v3/guide/gettingStarted.adoc | 2 +-
.../using-hal-with-json-views/v3/guide/links.adoc | 2 +-
.../v3/guide/runningTheApp.adoc | 2 +-
.../v3/guide/templates.adoc | 2 +-
.../v4/guide/buildingApi.adoc | 2 +-
.../v4/guide/gettingStarted.adoc | 2 +-
.../using-hal-with-json-views/v4/guide/links.adoc | 2 +-
.../v4/guide/runningTheApp.adoc | 2 +-
.../v4/guide/templates.adoc | 2 +-
.../v3/guide/generateTheApp.adoc | 2 +-
.../v4/guide/generateTheApp.adoc | 2 +-
guides/vaadin-grails/v4/guide/aboutVaadin.adoc | 2 +-
guides/vaadin-grails/v4/guide/profile.adoc | 2 +-
posts/2016-05-28.md | 2 +-
posts/2016-05-31.md | 2 +-
posts/2016-09-28.md | 2 +-
posts/2017-04-02.md | 2 +-
posts/2017-07-26.md | 4 +-
posts/2018-05-24.md | 2 +-
templates/partials/site-header.html | 2 +-
239 files changed, 358 insertions(+), 358 deletions(-)
diff --git a/buildSrc/src/main/template/style/guideItem.html b/buildSrc/src/main/template/style/guideItem.html
index 4f4c1d396b6..a20e6c1d73e 100644
--- a/buildSrc/src/main/template/style/guideItem.html
+++ b/buildSrc/src/main/template/style/guideItem.html
@@ -43,7 +43,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/inte [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa. [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/buildSrc/src/main/template/style/layout.html b/buildSrc/src/main/template/style/layout.html
index 1b8665578d3..1c0139b8a02 100644
--- a/buildSrc/src/main/template/style/layout.html
+++ b/buildSrc/src/main/template/style/layout.html
@@ -43,7 +43,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/ [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.k [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/buildSrc/src/main/template/style/menu.html b/buildSrc/src/main/template/style/menu.html
index 85ed873c6e2..d8838deda5c 100644
--- a/buildSrc/src/main/template/style/menu.html
+++ b/buildSrc/src/main/template/style/menu.html
@@ -33,7 +33,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/ [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.k [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/buildSrc/src/main/template/style/referenceItem.html b/buildSrc/src/main/template/style/referenceItem.html
index 920c9ea7c7d..10f0ca77960 100644
--- a/buildSrc/src/main/template/style/referenceItem.html
+++ b/buildSrc/src/main/template/style/referenceItem.html
@@ -48,7 +48,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/inte [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa. [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/guides/adding-commit-info/v3/guide/buildInfoPlugin.adoc b/guides/adding-commit-info/v3/guide/buildInfoPlugin.adoc
index ebe63151d10..faa932fd880 100644
--- a/guides/adding-commit-info/v3/guide/buildInfoPlugin.adoc
+++ b/guides/adding-commit-info/v3/guide/buildInfoPlugin.adoc
@@ -1,4 +1,4 @@
-Another popular approach that was popular with Grails 2.x was to utilize the https://grails.org/plugin/build-info[Build Info Plugin]
+Another popular approach that was popular with Grails 2.x was to utilize the https://grails.apache.org/plugins.html[Build Info Plugin]
The build-info plugin works by utilizing the environment variables available via a build system like Jenkins.
* BUILD_NUMBER
diff --git a/guides/adding-commit-info/v3/guide/perEnvironmentConfig.adoc b/guides/adding-commit-info/v3/guide/perEnvironmentConfig.adoc
index d6ba97890ab..d28221f7d25 100644
--- a/guides/adding-commit-info/v3/guide/perEnvironmentConfig.adoc
+++ b/guides/adding-commit-info/v3/guide/perEnvironmentConfig.adoc
@@ -1,7 +1,7 @@
Adding git commit information to your application is handy for debugging and transparency. The default simple mode only exposes the sha, time and branch name.
There are some organizations who would would prefer to restrict commit info even further in their more sensitive environments.
-One approach is to leverage http://docs.grails.org/latest/guide/conf.html#environments[per-environment configuration]
+One approach is to leverage https://grails.apache.org/docs/latest/guide/conf.html#environments[per-environment configuration]
to enable/disable and configure the endpoints differently according to the environment.
For example if you only wanted simple mode enabled in production you might use the following config:
diff --git a/guides/adding-commit-info/v4/guide/buildInfoPlugin.adoc b/guides/adding-commit-info/v4/guide/buildInfoPlugin.adoc
index ebe63151d10..faa932fd880 100644
--- a/guides/adding-commit-info/v4/guide/buildInfoPlugin.adoc
+++ b/guides/adding-commit-info/v4/guide/buildInfoPlugin.adoc
@@ -1,4 +1,4 @@
-Another popular approach that was popular with Grails 2.x was to utilize the https://grails.org/plugin/build-info[Build Info Plugin]
+Another popular approach that was popular with Grails 2.x was to utilize the https://grails.apache.org/plugins.html[Build Info Plugin]
The build-info plugin works by utilizing the environment variables available via a build system like Jenkins.
* BUILD_NUMBER
diff --git a/guides/adding-commit-info/v4/guide/perEnvironmentConfig.adoc b/guides/adding-commit-info/v4/guide/perEnvironmentConfig.adoc
index d6ba97890ab..d28221f7d25 100644
--- a/guides/adding-commit-info/v4/guide/perEnvironmentConfig.adoc
+++ b/guides/adding-commit-info/v4/guide/perEnvironmentConfig.adoc
@@ -1,7 +1,7 @@
Adding git commit information to your application is handy for debugging and transparency. The default simple mode only exposes the sha, time and branch name.
There are some organizations who would would prefer to restrict commit info even further in their more sensitive environments.
-One approach is to leverage http://docs.grails.org/latest/guide/conf.html#environments[per-environment configuration]
+One approach is to leverage https://grails.apache.org/docs/latest/guide/conf.html#environments[per-environment configuration]
to enable/disable and configure the endpoints differently according to the environment.
For example if you only wanted simple mode enabled in production you might use the following config:
diff --git a/guides/building-a-react-app/v4/guide/customizingApi.adoc b/guides/building-a-react-app/v4/guide/customizingApi.adoc
index 0296cec5951..fd98c622113 100644
--- a/guides/building-a-react-app/v4/guide/customizingApi.adoc
+++ b/guides/building-a-react-app/v4/guide/customizingApi.adoc
@@ -12,7 +12,7 @@ Connection: close
{"id":1,"name":"Pickup","make":{"id":1},"driver":{"id":1}}
----
-This is sufficient for many usages, but we'll need to get a bit more data for our React component in a moment. This is an excellent place for http://views.grails.org/latest/[JSON Views]. Let's create a new JSON view to render our Vehicle list:
+This is sufficient for many usages, but we'll need to get a bit more data for our React component in a moment. This is an excellent place for https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views]. Let's create a new JSON view to render our Vehicle list:
[source,bash]
----
diff --git a/guides/building-a-vue-app/v4/guide/customizingApi.adoc b/guides/building-a-vue-app/v4/guide/customizingApi.adoc
index 7bc2f64240b..c3fea9b373d 100644
--- a/guides/building-a-vue-app/v4/guide/customizingApi.adoc
+++ b/guides/building-a-vue-app/v4/guide/customizingApi.adoc
@@ -13,7 +13,7 @@ Connection: close
{"id":1,"name":"Pickup","make":{"id":1},"driver":{"id":1}}
----
-This is standard for many REST APIs, but we'll need to get a bit more data from this endpoint for our Vue app in a moment. This is an excellent scenario for http://views.grails.org/latest/[JSON Views]. Let's create a new JSON view to render our Vehicle list:
+This is standard for many REST APIs, but we'll need to get a bit more data from this endpoint for our Vue app in a moment. This is an excellent scenario for https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views]. Let's create a new JSON view to render our Vehicle list:
[source,bash]
----
diff --git a/guides/building-a-vue-app/v4/guide/gettingStarted.adoc b/guides/building-a-vue-app/v4/guide/gettingStarted.adoc
index bb29d8ccd3c..bee9f17eb6c 100644
--- a/guides/building-a-vue-app/v4/guide/gettingStarted.adoc
+++ b/guides/building-a-vue-app/v4/guide/gettingStarted.adoc
@@ -1,3 +1,3 @@
-In this guide we will build a Grails application with a Vue.js app as the frontend, using the https://grails-profiles.github.io/vue/latest/guide/index.html[Vue profile]. The example project will be the `Garage` application as seen in the http://guides.grails.org/building-a-react-app/guide/index.html[React] and http://guides.grails.org/vaadin-grails/guide/index.html[Vaadin] guides. You can refer to those guides for comparison with the Vue.js version.
+In this guide we will build a Grails application with a Vue.js app as the frontend, using the https://grails-profiles.github.io/vue/latest/guide/index.html[Vue profile]. The example project will be the `Garage` application as seen in the https://grails.apache.org/guides/building-a-react-app/guide/index.html[React] and https://grails.apache.org/guides/vaadin-grails/guide/index.html[Vaadin] guides. You can refer to those guides for comparison with the Vue.js version.
Please note that this guide is not an introduction to Vue.js. You can refer to the https://vuejs.org/v2/guide/[official documentation], or see this https://objectcomputing.com/resources/publications/sett/january-2018-room-with-a-vue-part-1[introductory article].
\ No newline at end of file
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
index 5a91c35f368..f93de8de2ec 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
@@ -1,8 +1,8 @@
-We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
-Grails simplifies the creation of domain classes with the http://docs.grails.org/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
+Grails simplifies the creation of domain classes with the https://grails.apache.org/docs/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
[source,bash]
----
./grailsw create-domain-class Announcement
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
index 0eaf3f7856a..e6abdfeef44 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html[Grails makes testing easier] from low-level unit testing to high
+https://grails.apache.org/docs/latest/guide/testing.html[Grails makes testing easier] from low-level unit testing to high
level functional tests.
We are going to test the constraints we defined in the Announcement domain Class in constraints property. In particular
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
index ec0603fb36a..ed00b5284da 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
-In this guide you are going to build a http://grails.org[Grails application] which will serve as a company intranet backend.
+In this guide you are going to build a https://grails.apache.org[Grails application] which will serve as a company intranet backend.
It exposes a JSON API of company announcements.
Additionally, you are going to build an https://developer.android.com/index.html[Android App], the intranet client, which
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
index 65870c0e6d0..d1398f21c90 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
@@ -1,4 +1,4 @@
-We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends http://docs.grails.org/latest/guide/webServices.html#restfulControllers[RestfulController]. This
+We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends https://grails.apache.org/docs/latest/guide/webServices.html#restfulControllers[RestfulController]. This
will provide us RESTful functionality to list, create, update and delete `Announcement` resources using
different HTTP Methods.
@@ -16,7 +16,7 @@ include::../snippets/grails-app/controllers/intranet/backend/v1/AnnouncementCont
We want our endpoint to listen in `/announcements` instead of `/announcement`. Moreover, we want the previous controller for
which we declared a namespace of v1 to handle the requests with the Accept-Version Http Header set to 1.0.
-Grails enables powerful http://docs.grails.org/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
+Grails enables powerful https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
do that. Add the next line to the mappings closure:
[source,groovy]
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
index d396e1c8b38..0f405c98535 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
+https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
requests against the running application and verifying the resultant behavior.
We use the https://github.com/grails-plugins/grails-rest-client-builder[Rest Client Builder Grails Plugin] whose
diff --git a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/versioning.adoc b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
index 15a172729be..f1919561e60 100644
--- a/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
+++ b/guides/building-an-android-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
@@ -2,7 +2,7 @@ It is important to think about API versioning from the beginning, especially whe
consumed by mobile phone applications. Users will run different versions of the app, and you will need to version
your API to create advanced functionality but keep supporting legacy versions.
-Grails allows multiple ways to http://docs.grails.org/latest/guide/webServices.html#versioningResources[Version REST Resources].
+Grails allows multiple ways to https://grails.apache.org/docs/latest/guide/webServices.html#versioningResources[Version REST Resources].
* Using the URI
* Using the Accept-Version Header
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
index 5a91c35f368..f93de8de2ec 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
@@ -1,8 +1,8 @@
-We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
-Grails simplifies the creation of domain classes with the http://docs.grails.org/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
+Grails simplifies the creation of domain classes with the https://grails.apache.org/docs/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
[source,bash]
----
./grailsw create-domain-class Announcement
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
index e070f4b8082..bfbf05e8a6a 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html[Grails makes testing easier] from low level unit testing to high
+https://grails.apache.org/docs/latest/guide/testing.html[Grails makes testing easier] from low level unit testing to high
level functional tests.
We are going to test the constraints we defined in the Announcement domain Class in constraints property. In particular
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
index 7417e45fb5b..904a3c953a7 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
-In this guide you are going to build a http://grails.org[Grails application] which will serve as a company intranet backend.
+In this guide you are going to build a https://grails.apache.org[Grails application] which will serve as a company intranet backend.
It exposes a JSON API of company announcements.
Additionally, you are going to build an https://developer.apple.com/ios/[iOS App], the intranet client, which
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
index 5d61af970fd..dc1be2d99c1 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
@@ -1,4 +1,4 @@
-We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends http://docs.grails.org/latest/guide/webServices.html#restfulControllers[RestfulController]. This
+We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends https://grails.apache.org/docs/latest/guide/webServices.html#restfulControllers[RestfulController]. This
will provide us RESTful functionality to list, create, update and delete `Announcement` resources using
different HTTP Methods.
@@ -16,7 +16,7 @@ include::../snippets/grails-app/controllers/intranet/backend/v1/AnnouncementCont
We want our endpoint to listen in /announcements instead of /announcement. Moreover, we want previous controller for
which we declared a namespace of v1 to handle the requests with the Accept-Version Http Header set to 1.0.
-Grails enables powerful http://docs.grails.org/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
+Grails enables powerful https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
do that. Add the next line to the mappings closure:
[source,groovy]
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
index de96d1b1dbf..aba7cb46924 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
+https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
requests against the running application and verifying the resultant behavior.
We use the https://github.com/grails-plugins/grails-rest-client-builder[Rest Client Builder Grails Plugin] whose
diff --git a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/versioning.adoc b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
index 29798f23e9b..1d51f00cb89 100644
--- a/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
+++ b/guides/building-an-ios-objectc-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
@@ -2,7 +2,7 @@ It is important to think about API versioning from the beginning, especially whe
consumed by mobile phone applications. Users will run different versions of the app, and you will need to version
your API to create advanced functionality but keep supporting legacy versions.
-Grails allows multiple ways to http://docs.grails.org/latest/guide/webServices.html#versioningResources[Version REST Resources].
+Grails allows multiple ways to https://grails.apache.org/docs/latest/guide/webServices.html#versioningResources[Version REST Resources].
* Using the URI
* Using the Accept-Version Header
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
index 5a91c35f368..f93de8de2ec 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClass.adoc
@@ -1,8 +1,8 @@
-We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+We need to create persistent entities to store company announcements. Grails handles persistence with the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
-Grails simplifies the creation of domain classes with the http://docs.grails.org/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
+Grails simplifies the creation of domain classes with the https://grails.apache.org/docs/latest/ref/Command%20Line/create-domain-class.html[create-domain-class command].
[source,bash]
----
./grailsw create-domain-class Announcement
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
index e070f4b8082..bfbf05e8a6a 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/domainClassTest.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html[Grails makes testing easier] from low level unit testing to high
+https://grails.apache.org/docs/latest/guide/testing.html[Grails makes testing easier] from low level unit testing to high
level functional tests.
We are going to test the constraints we defined in the Announcement domain Class in constraints property. In particular
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
index 7417e45fb5b..904a3c953a7 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
-In this guide you are going to build a http://grails.org[Grails application] which will serve as a company intranet backend.
+In this guide you are going to build a https://grails.apache.org[Grails application] which will serve as a company intranet backend.
It exposes a JSON API of company announcements.
Additionally, you are going to build an https://developer.apple.com/ios/[iOS App], the intranet client, which
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
index 5d61af970fd..dc1be2d99c1 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1Controller.adoc
@@ -1,4 +1,4 @@
-We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends http://docs.grails.org/latest/guide/webServices.html#restfulControllers[RestfulController]. This
+We create a _Controller_ for the _Domain class_ we previously created. Our Controller extends https://grails.apache.org/docs/latest/guide/webServices.html#restfulControllers[RestfulController]. This
will provide us RESTful functionality to list, create, update and delete `Announcement` resources using
different HTTP Methods.
@@ -16,7 +16,7 @@ include::../snippets/grails-app/controllers/intranet/backend/v1/AnnouncementCont
We want our endpoint to listen in /announcements instead of /announcement. Moreover, we want previous controller for
which we declared a namespace of v1 to handle the requests with the Accept-Version Http Header set to 1.0.
-Grails enables powerful http://docs.grails.org/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
+Grails enables powerful https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappingss[URL mapping] configuration to
do that. Add the next line to the mappings closure:
[source,groovy]
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
index 6417841380b..43d3c483273 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/v1FunctionalTests.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
+https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
requests against the running application and verifying the resultant behavior.
We use the https://github.com/grails-plugins/grails-rest-client-builder[Rest Client Builder Grails Plugin] whose
diff --git a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/versioning.adoc b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
index 29798f23e9b..1d51f00cb89 100644
--- a/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
+++ b/guides/building-an-ios-swift-client-powered-by-a-grails-backend/v4/guide/versioning.adoc
@@ -2,7 +2,7 @@ It is important to think about API versioning from the beginning, especially whe
consumed by mobile phone applications. Users will run different versions of the app, and you will need to version
your API to create advanced functionality but keep supporting legacy versions.
-Grails allows multiple ways to http://docs.grails.org/latest/guide/webServices.html#versioningResources[Version REST Resources].
+Grails allows multiple ways to https://grails.apache.org/docs/latest/guide/webServices.html#versioningResources[Version REST Resources].
* Using the URI
* Using the Accept-Version Header
diff --git a/guides/command-objects-and-forms/v3/guide/addCreateAndSaveActions.adoc b/guides/command-objects-and-forms/v3/guide/addCreateAndSaveActions.adoc
index f267e918f18..618322a9dff 100644
--- a/guides/command-objects-and-forms/v3/guide/addCreateAndSaveActions.adoc
+++ b/guides/command-objects-and-forms/v3/guide/addCreateAndSaveActions.adoc
@@ -31,7 +31,7 @@ validate the object. All of these tasks could be done manually, but by making us
command object, all of this behavior is automatic and leaves your code uncluttered of so
much boilerplate.
-Arguably, the best feature here is http://docs.grails.org/latest/guide/theWebLayer.html#dataBinding[Data Binding],
+Arguably, the best feature here is https://grails.apache.org/docs/latest/guide/theWebLayer.html#dataBinding[Data Binding],
part of the automatic behavior you get from using command objects. While on the create
page, view the HTML source code (generated from the compiled `create.gsp`) and look for
the `<form>` tag:
diff --git a/guides/command-objects-and-forms/v3/guide/gettingStarted.adoc b/guides/command-objects-and-forms/v3/guide/gettingStarted.adoc
index 3d98cd9ba7e..5f7b744aadf 100644
--- a/guides/command-objects-and-forms/v3/guide/gettingStarted.adoc
+++ b/guides/command-objects-and-forms/v3/guide/gettingStarted.adoc
@@ -1,5 +1,5 @@
In this guide you are going to use
-http://docs.grails.org/latest/guide/theWebLayer.html#commandObjects[Command Objects]
+https://grails.apache.org/docs/latest/guide/theWebLayer.html#commandObjects[Command Objects]
to process form submissions with automatic type conversion, custom validation, and
simple error handling.
diff --git a/guides/command-objects-and-forms/v3/guide/whatAreCommandObjects.adoc b/guides/command-objects-and-forms/v3/guide/whatAreCommandObjects.adoc
index a130eca9a4f..d52630cbf8d 100644
--- a/guides/command-objects-and-forms/v3/guide/whatAreCommandObjects.adoc
+++ b/guides/command-objects-and-forms/v3/guide/whatAreCommandObjects.adoc
@@ -1,4 +1,4 @@
-As described in the http://docs.grails.org/latest/guide/theWebLayer.html#commandObjects[Grails documentation],
+As described in the https://grails.apache.org/docs/latest/guide/theWebLayer.html#commandObjects[Grails documentation],
____
A command object is a class that is used in conjunction with data binding, usually to
allow validation of data that may not fit into an existing domain class. *A class is only
diff --git a/guides/command-objects-and-forms/v4/guide/addCreateAndSaveActions.adoc b/guides/command-objects-and-forms/v4/guide/addCreateAndSaveActions.adoc
index 049acf1a6a8..9d2347e2f39 100644
--- a/guides/command-objects-and-forms/v4/guide/addCreateAndSaveActions.adoc
+++ b/guides/command-objects-and-forms/v4/guide/addCreateAndSaveActions.adoc
@@ -31,7 +31,7 @@ validate the object. All of these tasks could be done manually, but by making us
command object, all of this behavior is automatic and leaves your code uncluttered of so
much boilerplate.
-Arguably, the best feature here is http://docs.grails.org/latest/guide/theWebLayer.html#dataBinding[Data Binding],
+Arguably, the best feature here is https://grails.apache.org/docs/latest/guide/theWebLayer.html#dataBinding[Data Binding],
part of the automatic behavior you get from using command objects. While on the create
page, view the HTML source code (generated from the compiled `create.gsp`) and look for
the `<form>` tag:
diff --git a/guides/command-objects-and-forms/v4/guide/gettingStarted.adoc b/guides/command-objects-and-forms/v4/guide/gettingStarted.adoc
index 3d98cd9ba7e..5f7b744aadf 100644
--- a/guides/command-objects-and-forms/v4/guide/gettingStarted.adoc
+++ b/guides/command-objects-and-forms/v4/guide/gettingStarted.adoc
@@ -1,5 +1,5 @@
In this guide you are going to use
-http://docs.grails.org/latest/guide/theWebLayer.html#commandObjects[Command Objects]
+https://grails.apache.org/docs/latest/guide/theWebLayer.html#commandObjects[Command Objects]
to process form submissions with automatic type conversion, custom validation, and
simple error handling.
diff --git a/guides/command-objects-and-forms/v4/guide/whatAreCommandObjects.adoc b/guides/command-objects-and-forms/v4/guide/whatAreCommandObjects.adoc
index a130eca9a4f..d52630cbf8d 100644
--- a/guides/command-objects-and-forms/v4/guide/whatAreCommandObjects.adoc
+++ b/guides/command-objects-and-forms/v4/guide/whatAreCommandObjects.adoc
@@ -1,4 +1,4 @@
-As described in the http://docs.grails.org/latest/guide/theWebLayer.html#commandObjects[Grails documentation],
+As described in the https://grails.apache.org/docs/latest/guide/theWebLayer.html#commandObjects[Grails documentation],
____
A command object is a class that is used in conjunction with data binding, usually to
allow validation of data that may not fit into an existing domain class. *A class is only
diff --git a/guides/common/common-functionalTestsIntro.adoc b/guides/common/common-functionalTestsIntro.adoc
index 5a5d4278f3d..d0bdf8d621a 100644
--- a/guides/common/common-functionalTestsIntro.adoc
+++ b/guides/common/common-functionalTestsIntro.adoc
@@ -1,2 +1,2 @@
-http://docs.grails.org/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
+https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[Functional Tests] involve making HTTP
requests against the running application and verifying the resultant behaviour.
diff --git a/guides/common/common-installGrails5.adoc b/guides/common/common-installGrails5.adoc
index 1dbd086778c..df14a189096 100644
--- a/guides/common/common-installGrails5.adoc
+++ b/guides/common/common-installGrails5.adoc
@@ -33,7 +33,7 @@ NOTE: If you are running Windows, there is a clone project of `sdkman` available
This is not the recommend way to install Grails, but here are the manual installation steps, if the above methods fails.
-Download the Grails binary package from https://grails.org/download.html[https://grails.org]. Unpack the package in a convenient directory.
+Download the Grails binary package from https://grails.apache.org/download.html[https://grails.apache.org]. Unpack the package in a convenient directory.
[source, bash]
----
diff --git a/guides/common/common-installingGrails-grails3.adoc b/guides/common/common-installingGrails-grails3.adoc
index 97d35460c4e..66ccb425498 100644
--- a/guides/common/common-installingGrails-grails3.adoc
+++ b/guides/common/common-installingGrails-grails3.adoc
@@ -34,7 +34,7 @@ NOTE: If you are running Windows, there is a clone project of `sdkman` available
This is not the recommend way to install Grails, but here are the manual installation steps, if the above methods fails.
-Download the Grails binary package from https://grails.org/download.html[https://grails.org]. Unpack the package in a convenient directory.
+Download the Grails binary package from https://grails.apache.org/download.html[https://grails.apache.org]. Unpack the package in a convenient directory.
[source, bash]
----
diff --git a/guides/common/common-installingGrails.adoc b/guides/common/common-installingGrails.adoc
index 196db6e925f..b0eab00408a 100644
--- a/guides/common/common-installingGrails.adoc
+++ b/guides/common/common-installingGrails.adoc
@@ -33,7 +33,7 @@ NOTE: If you are running Windows, there is a clone project of `sdkman` available
This is not the recommend way to install Grails, but here are the manual installation steps, if the above methods fails.
-Download the Grails binary package from https://grails.org/download.html[https://grails.org]. Unpack the package in a convenient directory.
+Download the Grails binary package from https://grails.apache.org/download.html[https://grails.apache.org]. Unpack the package in a convenient directory.
[source, bash]
----
diff --git a/guides/common/common-quoteTagLib.adoc b/guides/common/common-quoteTagLib.adoc
index f7c4e088864..10153094ddf 100644
--- a/guides/common/common-quoteTagLib.adoc
+++ b/guides/common/common-quoteTagLib.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/theWebLayer.html#taglibs[Grails Tag Libraries]
+https://grails.apache.org/docs/latest/guide/theWebLayer.html#taglibs[Grails Tag Libraries]
____
A tag library fulfills role of "view helper" in the Model View Controller (MVC) pattern and helps with GSP rendering. In Grails a tag library is a class with a name that ends in the convention "TagLib" and lives in the grails-app/taglib directory. Use the create-tag-lib command create a tag library
___
diff --git a/guides/common/common-tipScaffolding.adoc b/guides/common/common-tipScaffolding.adoc
index 5229dac48e1..58e6d083291 100644
--- a/guides/common/common-tipScaffolding.adoc
+++ b/guides/common/common-tipScaffolding.adoc
@@ -1 +1 @@
-TIP: Learn more about scaffolding in the http://docs.grails.org/latest/guide/scaffolding.html[Grails documentation].
+TIP: Learn more about scaffolding in the https://grails.apache.org/docs/latest/guide/scaffolding.html[Grails documentation].
diff --git a/guides/creating-your-first-grails-app/v3/guide/applicationProfile.adoc b/guides/creating-your-first-grails-app/v3/guide/applicationProfile.adoc
index 90f11eb0f49..f64c01ef7d9 100644
--- a/guides/creating-your-first-grails-app/v3/guide/applicationProfile.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/applicationProfile.adoc
@@ -1,7 +1,7 @@
-You can optionally specify a http://docs.grails.org/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
+You can optionally specify a https://grails.apache.org/docs/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
-To view of a list of what profiles are available, use the http://docs.grails.org/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
+To view of a list of what profiles are available, use the https://grails.apache.org/docs/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
[source, bash]
----
@@ -36,7 +36,7 @@ You may optionally specify a package and version (defaults to `org.grails.profil
grails create-app myApp -profile org.grails.profiles:react:1.0.2
----
-To get detailed information about a profile use the http://docs.grails.org/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
+To get detailed information about a profile use the https://grails.apache.org/docs/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v3/guide/console.adoc b/guides/creating-your-first-grails-app/v3/guide/console.adoc
index 142b2a4da02..d9eab9856fa 100644
--- a/guides/creating-your-first-grails-app/v3/guide/console.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/console.adoc
@@ -1,6 +1,6 @@
-Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the http://docs.grails.org/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
+Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the https://grails.apache.org/docs/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
-If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
+If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
Launch the Grails Console:
diff --git a/guides/creating-your-first-grails-app/v3/guide/controllers.adoc b/guides/creating-your-first-grails-app/v3/guide/controllers.adoc
index e1006cf534a..177da6e7c61 100644
--- a/guides/creating-your-first-grails-app/v3/guide/controllers.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/controllers.adoc
@@ -1,6 +1,6 @@
This section will focus on the basics of creating a controller and defining actions.
-TIP: While not part of the "MVC" triad, Grails also provides support for http://docs.grails.org/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
+TIP: While not part of the "MVC" triad, Grails also provides support for https://grails.apache.org/docs/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
Following the convention over configuration principle, Grails will configure any Groovy classes under `grails-app/controllers/` as controllers, without any additional configuration. You can create the Groovy class yourself, or use the `create-controller` command to generate the controller and an associated test spec.
@@ -27,7 +27,7 @@ class HomeController {
}
----
-Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the http://docs.grails.org/latest/guide/theWebLay [...]
+Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the https://grails.apache.org/docs/latest/guide/t [...]
We don't have any need for logic in this particular action just yet, but we would like it to render a page. We'll look at GSP pages in more detail in the <<Views>> section, but for now, let's create a very simple GSP page for our `HomeController.index` action to display.
diff --git a/guides/creating-your-first-grails-app/v3/guide/createApp.adoc b/guides/creating-your-first-grails-app/v3/guide/createApp.adoc
index 1e8e61aeeca..b3ca8033f0d 100644
--- a/guides/creating-your-first-grails-app/v3/guide/createApp.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/createApp.adoc
@@ -1,4 +1,4 @@
-Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the http://docs.grails.org/latest/ref/Command%20Line/create-app.html[`create-app`] command:
+Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the https://grails.apache.org/docs/latest/ref/Command%20Line/create-app.html[`create-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v3/guide/creatingDomainClass.adoc b/guides/creating-your-first-grails-app/v3/guide/creatingDomainClass.adoc
index d146c46d7e9..0b9464dcc73 100644
--- a/guides/creating-your-first-grails-app/v3/guide/creatingDomainClass.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/creatingDomainClass.adoc
@@ -44,4 +44,4 @@ class Vehicle {
<1> Properties will be used to create columns in the database (assuming a relational database is used)
<2> Constraints are used to enforce valid data in each field - Grails provides a rich set of constraints for common scenarios, and you can define custom constraints as well
-Please see the Grails documentation for a complete list and documentation of how to use https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://docs.grails.org/latest/ref/Constraints/Usage.html[constraints]
+Please see the Grails documentation for a complete list and documentation of how to use https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://grails.apache.org/docs/latest/ref/Constraints/Usage.html[constraints]
diff --git a/guides/creating-your-first-grails-app/v3/guide/deployment.adoc b/guides/creating-your-first-grails-app/v3/guide/deployment.adoc
index a8873526dec..ad0bc77cecc 100644
--- a/guides/creating-your-first-grails-app/v3/guide/deployment.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/deployment.adoc
@@ -11,7 +11,7 @@ BUILD SUCCESSFUL
[TIP]
====
-We didn't cover the topic of http://docs.grails.org/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "production" envi [...]
+We didn't cover the topic of https://grails.apache.org/docs/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "producti [...]
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v3/guide/gspLinks.adoc b/guides/creating-your-first-grails-app/v3/guide/gspLinks.adoc
index d2b192b21f5..094cc19c594 100644
--- a/guides/creating-your-first-grails-app/v3/guide/gspLinks.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/gspLinks.adoc
@@ -6,4 +6,4 @@ Let's take a look at one more common GSP tag: `<g:link>`
include::../snippets/grails-app/views/home/index.gsp[indent=0,lines="34..36"]
----
-`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the http://docs.grails.org/latest/ref/Tags/link [...]
+`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the https://grails.apache.org/docs/latest/ref/T [...]
diff --git a/guides/creating-your-first-grails-app/v3/guide/respond.adoc b/guides/creating-your-first-grails-app/v3/guide/respond.adoc
index f2e2bde7fac..4a39af41256 100644
--- a/guides/creating-your-first-grails-app/v3/guide/respond.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/respond.adoc
@@ -22,7 +22,7 @@ class HomeController {
}
----
<1> We're calling the `respond` method to render a Groovy map of content to the requestor, containing a `name` property from the session (defaulting to "User" if no session value exists) and the current total of `Vehicle` instances from GORM's `count` method.
-<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://docs.grails.org/latest/ref/Controllers/session.html[Grails documentation].
+<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://grails.apache.org/docs/latest/ref/Controllers/session.html[Grails documentation].
<3> We're using `flash` scope to set a message to display upon the next request
<4> We don't have any specific content to display in this action, so we issue a redirect back to the `index` action (note that in Groovy method parenthesis are optional so long as there is at least one argument).
diff --git a/guides/creating-your-first-grails-app/v3/guide/runningTheApp.adoc b/guides/creating-your-first-grails-app/v3/guide/runningTheApp.adoc
index 076ff536375..97b16910c9a 100644
--- a/guides/creating-your-first-grails-app/v3/guide/runningTheApp.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/runningTheApp.adoc
@@ -1,6 +1,6 @@
Now that you've created (or downloaded) your Grails project, it's time to run it and see what Grails has already given you.
-If you have a local installation of Grails, you can run the app using the http://docs.grails.org/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
+If you have a local installation of Grails, you can run the app using the https://grails.apache.org/docs/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
[source, bash]
----
@@ -9,7 +9,7 @@ $ cd myApp/
**Run the App without Grails Installed**
-Thanks to the http://docs.grails.org/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
+Thanks to the https://grails.apache.org/docs/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
Grails installed. If you download it from the http://start.grails.org[Grails Application Forge], the Grails Wrapper is included too.
[source, bash]
@@ -28,7 +28,7 @@ $ grails run-app
**Run the App with Grails Interactive Mode**
-You can also use Grails' http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
+You can also use Grails' https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
In this guide we will be preferring the Grails wrapper for most commands.
diff --git a/guides/creating-your-first-grails-app/v3/guide/services.adoc b/guides/creating-your-first-grails-app/v3/guide/services.adoc
index 12b6ba98db5..674c2343ba8 100644
--- a/guides/creating-your-first-grails-app/v3/guide/services.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/services.adoc
@@ -75,6 +75,6 @@ Now, on the `show` page, we can access the `estimatedValue` property and display
----
include::../snippets/grails-app/views/vehicle/show.gsp[indent=0,lines="17..20"]
----
-<1> `<g:formatNumber>` is another GSP tag which provides many useful options for rendering numbers, including currency and decimal precision. See the http://docs.grails.org/latest/ref/Tags/formatNumber.html[Grails documentation] for more.
+<1> `<g:formatNumber>` is another GSP tag which provides many useful options for rendering numbers, including currency and decimal precision. See the https://grails.apache.org/docs/latest/ref/Tags/formatNumber.html[Grails documentation] for more.
Restart the application and browse to the show page for a `Vehicle`, such as `http://localhost:8080/vehicle/show/1`. You should see the "Estimated Value" on the page
\ No newline at end of file
diff --git a/guides/creating-your-first-grails-app/v3/guide/staticScaffolding.adoc b/guides/creating-your-first-grails-app/v3/guide/staticScaffolding.adoc
index 061f07628f9..02cb8a45058 100644
--- a/guides/creating-your-first-grails-app/v3/guide/staticScaffolding.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/staticScaffolding.adoc
@@ -39,12 +39,12 @@ Open the `VehicleController.groovy` file at `grails-app/controllers/org/grails/g
include::../snippets/grails-app/controllers/org/grails/guides/scaffolding/VehicleController.groovy[indent=0,lines="4..8,10..114"]
----
-<1> The http://docs.grails.org/latest/api/grails/transaction/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the http://docs.grails.org/latest/guide/single.html#declarativeTransactions[Grails documentation]
-<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://docs.grails.org/latest/ref/Controllers/params.html[Grails documentation] for more detail.
-<3> The `respond` method takes an object to return to the requestor, using https://docs.grails.org/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://docs.grails.org/latest/ref/Controllers/respond.ht [...]
-<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://docs.grails.org/latest/ref/Controllers/request.html[Grails documentation on `request`].
-<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://docs.grails.org/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
-<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://docs.grails.org/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
-<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://docs.grails.org/latest/ref/Controllers/render.html[Grails documentation].
+<1> The https://grails.apache.org/docs/latest/api/grails/transaction/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the https://grails.apache.org/docs/latest/guide/single.html#declarativeTransactions[Grails do [...]
+<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://grails.apache.org/docs/latest/ref/Controllers/params.html[Grails documentation] for more detail.
+<3> The `respond` method takes an object to return to the requestor, using https://grails.apache.org/docs/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://grails.apache.org/docs/latest/ref/Controll [...]
+<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://grails.apache.org/docs/latest/ref/Controllers/request.html[Grails documentation on `request`].
+<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://grails.apache.org/docs/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
+<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://grails.apache.org/docs/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
+<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://grails.apache.org/docs/latest/ref/Controllers/render.html[Grails documentation].
That's a lot of code! Generating and modifying a scaffold controller is a good learning exercise, so feel free to experiment and modify this code - you can always revert back to the version in the `completed` project of this guide.
diff --git a/guides/creating-your-first-grails-app/v3/guide/testing.adoc b/guides/creating-your-first-grails-app/v3/guide/testing.adoc
index f51123657e2..dd66193bae7 100644
--- a/guides/creating-your-first-grails-app/v3/guide/testing.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/testing.adoc
@@ -1,4 +1,4 @@
-Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. http://docs.grails.org/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. http://docs.grails.org/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up and running, and [...]
+Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. https://grails.apache.org/docs/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. https://grails.apache.org/docs/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up a [...]
The testing framework used by Grails is http://spockframework.org[Spock]. Spock provides an expressive syntax for writing test cases, based on the Groovy language, and so is a great fit for Grails. It includes a JUnit runner, which means IDE support is effectively universal (any IDE that can run JUnit tests can run Spock tests).
@@ -6,7 +6,7 @@ TIP: Spock is a rich framework (even outside of Grails applications) and well wo
Grails tests are stored (by convention) in the `src/test/groovy` directory (unit tests) and `src/integration-test/groovy` directory (integration/functional tests).
-You can run your Grails tests using the http://docs.grails.org/latest/ref/Command%20Line/test-app.html[`test-app`] command:
+You can run your Grails tests using the https://grails.apache.org/docs/latest/ref/Command%20Line/test-app.html[`test-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v3/guide/urlMappings.adoc b/guides/creating-your-first-grails-app/v3/guide/urlMappings.adoc
index 7c503a00541..b3402af8bf0 100644
--- a/guides/creating-your-first-grails-app/v3/guide/urlMappings.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/urlMappings.adoc
@@ -2,7 +2,7 @@ Now that we have our new "home" page, it would be nice if it was the app's landi
Grails uses the `UrlMappings.groovy` file to route request to the proper controller and action. They can be as simple as URI strings that redirect to a controller and/or action, or they can include wildcards and constraints and become quite sophisticated.
-TIP: Learn much more about URL Mappings from the http://docs.grails.org/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
+TIP: Learn much more about URL Mappings from the https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
Let's look at the default `URLMappings.groovy` file.
diff --git a/guides/creating-your-first-grails-app/v3/guide/views.adoc b/guides/creating-your-first-grails-app/v3/guide/views.adoc
index 842890913d2..0cf55047563 100644
--- a/guides/creating-your-first-grails-app/v3/guide/views.adoc
+++ b/guides/creating-your-first-grails-app/v3/guide/views.adoc
@@ -1,6 +1,6 @@
Views are the third component of the MVC pattern. Views are responsible for presenting data to the user (which might be a browser page, an API endpoint, or some other sort of consumer). In many apps, views are HTML pages designed to be loaded in a browser. However, it is perfectly reasonable for a "view" to be an XML or JSON document, depending on the type of client requesting the view.
-Grails' primary view technology is http://docs.grails.org/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, the GSP p [...]
+Grails' primary view technology is https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, t [...]
You've already worked with GSP views in this guide, but let's quickly cover the basics.
diff --git a/guides/creating-your-first-grails-app/v4/guide/applicationProfile.adoc b/guides/creating-your-first-grails-app/v4/guide/applicationProfile.adoc
index 90f11eb0f49..f64c01ef7d9 100644
--- a/guides/creating-your-first-grails-app/v4/guide/applicationProfile.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/applicationProfile.adoc
@@ -1,7 +1,7 @@
-You can optionally specify a http://docs.grails.org/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
+You can optionally specify a https://grails.apache.org/docs/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
-To view of a list of what profiles are available, use the http://docs.grails.org/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
+To view of a list of what profiles are available, use the https://grails.apache.org/docs/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
[source, bash]
----
@@ -36,7 +36,7 @@ You may optionally specify a package and version (defaults to `org.grails.profil
grails create-app myApp -profile org.grails.profiles:react:1.0.2
----
-To get detailed information about a profile use the http://docs.grails.org/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
+To get detailed information about a profile use the https://grails.apache.org/docs/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v4/guide/console.adoc b/guides/creating-your-first-grails-app/v4/guide/console.adoc
index 142b2a4da02..d9eab9856fa 100644
--- a/guides/creating-your-first-grails-app/v4/guide/console.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/console.adoc
@@ -1,6 +1,6 @@
-Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the http://docs.grails.org/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
+Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the https://grails.apache.org/docs/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
-If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
+If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
Launch the Grails Console:
diff --git a/guides/creating-your-first-grails-app/v4/guide/controllers.adoc b/guides/creating-your-first-grails-app/v4/guide/controllers.adoc
index e1006cf534a..177da6e7c61 100644
--- a/guides/creating-your-first-grails-app/v4/guide/controllers.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/controllers.adoc
@@ -1,6 +1,6 @@
This section will focus on the basics of creating a controller and defining actions.
-TIP: While not part of the "MVC" triad, Grails also provides support for http://docs.grails.org/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
+TIP: While not part of the "MVC" triad, Grails also provides support for https://grails.apache.org/docs/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
Following the convention over configuration principle, Grails will configure any Groovy classes under `grails-app/controllers/` as controllers, without any additional configuration. You can create the Groovy class yourself, or use the `create-controller` command to generate the controller and an associated test spec.
@@ -27,7 +27,7 @@ class HomeController {
}
----
-Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the http://docs.grails.org/latest/guide/theWebLay [...]
+Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the https://grails.apache.org/docs/latest/guide/t [...]
We don't have any need for logic in this particular action just yet, but we would like it to render a page. We'll look at GSP pages in more detail in the <<Views>> section, but for now, let's create a very simple GSP page for our `HomeController.index` action to display.
diff --git a/guides/creating-your-first-grails-app/v4/guide/createApp.adoc b/guides/creating-your-first-grails-app/v4/guide/createApp.adoc
index 1e8e61aeeca..b3ca8033f0d 100644
--- a/guides/creating-your-first-grails-app/v4/guide/createApp.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/createApp.adoc
@@ -1,4 +1,4 @@
-Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the http://docs.grails.org/latest/ref/Command%20Line/create-app.html[`create-app`] command:
+Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the https://grails.apache.org/docs/latest/ref/Command%20Line/create-app.html[`create-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v4/guide/creatingDomainClass.adoc b/guides/creating-your-first-grails-app/v4/guide/creatingDomainClass.adoc
index d146c46d7e9..0b9464dcc73 100644
--- a/guides/creating-your-first-grails-app/v4/guide/creatingDomainClass.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/creatingDomainClass.adoc
@@ -44,4 +44,4 @@ class Vehicle {
<1> Properties will be used to create columns in the database (assuming a relational database is used)
<2> Constraints are used to enforce valid data in each field - Grails provides a rich set of constraints for common scenarios, and you can define custom constraints as well
-Please see the Grails documentation for a complete list and documentation of how to use https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://docs.grails.org/latest/ref/Constraints/Usage.html[constraints]
+Please see the Grails documentation for a complete list and documentation of how to use https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://grails.apache.org/docs/latest/ref/Constraints/Usage.html[constraints]
diff --git a/guides/creating-your-first-grails-app/v4/guide/deployment.adoc b/guides/creating-your-first-grails-app/v4/guide/deployment.adoc
index a8873526dec..ad0bc77cecc 100644
--- a/guides/creating-your-first-grails-app/v4/guide/deployment.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/deployment.adoc
@@ -11,7 +11,7 @@ BUILD SUCCESSFUL
[TIP]
====
-We didn't cover the topic of http://docs.grails.org/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "production" envi [...]
+We didn't cover the topic of https://grails.apache.org/docs/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "producti [...]
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v4/guide/gspLinks.adoc b/guides/creating-your-first-grails-app/v4/guide/gspLinks.adoc
index d2b192b21f5..094cc19c594 100644
--- a/guides/creating-your-first-grails-app/v4/guide/gspLinks.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/gspLinks.adoc
@@ -6,4 +6,4 @@ Let's take a look at one more common GSP tag: `<g:link>`
include::../snippets/grails-app/views/home/index.gsp[indent=0,lines="34..36"]
----
-`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the http://docs.grails.org/latest/ref/Tags/link [...]
+`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the https://grails.apache.org/docs/latest/ref/T [...]
diff --git a/guides/creating-your-first-grails-app/v4/guide/respond.adoc b/guides/creating-your-first-grails-app/v4/guide/respond.adoc
index f2e2bde7fac..4a39af41256 100644
--- a/guides/creating-your-first-grails-app/v4/guide/respond.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/respond.adoc
@@ -22,7 +22,7 @@ class HomeController {
}
----
<1> We're calling the `respond` method to render a Groovy map of content to the requestor, containing a `name` property from the session (defaulting to "User" if no session value exists) and the current total of `Vehicle` instances from GORM's `count` method.
-<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://docs.grails.org/latest/ref/Controllers/session.html[Grails documentation].
+<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://grails.apache.org/docs/latest/ref/Controllers/session.html[Grails documentation].
<3> We're using `flash` scope to set a message to display upon the next request
<4> We don't have any specific content to display in this action, so we issue a redirect back to the `index` action (note that in Groovy method parenthesis are optional so long as there is at least one argument).
diff --git a/guides/creating-your-first-grails-app/v4/guide/runningTheApp.adoc b/guides/creating-your-first-grails-app/v4/guide/runningTheApp.adoc
index 076ff536375..97b16910c9a 100644
--- a/guides/creating-your-first-grails-app/v4/guide/runningTheApp.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/runningTheApp.adoc
@@ -1,6 +1,6 @@
Now that you've created (or downloaded) your Grails project, it's time to run it and see what Grails has already given you.
-If you have a local installation of Grails, you can run the app using the http://docs.grails.org/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
+If you have a local installation of Grails, you can run the app using the https://grails.apache.org/docs/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
[source, bash]
----
@@ -9,7 +9,7 @@ $ cd myApp/
**Run the App without Grails Installed**
-Thanks to the http://docs.grails.org/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
+Thanks to the https://grails.apache.org/docs/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
Grails installed. If you download it from the http://start.grails.org[Grails Application Forge], the Grails Wrapper is included too.
[source, bash]
@@ -28,7 +28,7 @@ $ grails run-app
**Run the App with Grails Interactive Mode**
-You can also use Grails' http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
+You can also use Grails' https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
In this guide we will be preferring the Grails wrapper for most commands.
diff --git a/guides/creating-your-first-grails-app/v4/guide/staticScaffolding.adoc b/guides/creating-your-first-grails-app/v4/guide/staticScaffolding.adoc
index 5b0bc4711f5..8d5a03da3a5 100644
--- a/guides/creating-your-first-grails-app/v4/guide/staticScaffolding.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/staticScaffolding.adoc
@@ -39,12 +39,12 @@ Open the `VehicleController.groovy` file at `grails-app/controllers/org/grails/g
include::../snippets/grails-app/controllers/org/grails/guides/scaffolding/VehicleController.groovy[indent=0,lines="4..8,10..114"]
----
-<1> The http://gorm.grails.org/latest/api/grails/gorm/transactions/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the http://docs.grails.org/latest/guide/single.html#declarativeTransactions[Grails documentation]
-<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://docs.grails.org/latest/ref/Controllers/params.html[Grails documentation] for more detail.
-<3> The `respond` method takes an object to return to the requestor, using https://docs.grails.org/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://docs.grails.org/latest/ref/Controllers/respond.ht [...]
-<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://docs.grails.org/latest/ref/Controllers/request.html[Grails documentation on `request`].
-<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://docs.grails.org/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
-<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://docs.grails.org/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
-<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://docs.grails.org/latest/ref/Controllers/render.html[Grails documentation].
+<1> The http://gorm.grails.org/latest/api/grails/gorm/transactions/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the https://grails.apache.org/docs/latest/guide/single.html#declarativeTransactions[Grails docu [...]
+<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://grails.apache.org/docs/latest/ref/Controllers/params.html[Grails documentation] for more detail.
+<3> The `respond` method takes an object to return to the requestor, using https://grails.apache.org/docs/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://grails.apache.org/docs/latest/ref/Controll [...]
+<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://grails.apache.org/docs/latest/ref/Controllers/request.html[Grails documentation on `request`].
+<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://grails.apache.org/docs/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
+<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://grails.apache.org/docs/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
+<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://grails.apache.org/docs/latest/ref/Controllers/render.html[Grails documentation].
That's a lot of code! Generating and modifying a scaffold controller is a good learning exercise, so feel free to experiment and modify this code - you can always revert back to the version in the `completed` project of this guide.
diff --git a/guides/creating-your-first-grails-app/v4/guide/testing.adoc b/guides/creating-your-first-grails-app/v4/guide/testing.adoc
index f51123657e2..dd66193bae7 100644
--- a/guides/creating-your-first-grails-app/v4/guide/testing.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/testing.adoc
@@ -1,4 +1,4 @@
-Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. http://docs.grails.org/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. http://docs.grails.org/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up and running, and [...]
+Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. https://grails.apache.org/docs/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. https://grails.apache.org/docs/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up a [...]
The testing framework used by Grails is http://spockframework.org[Spock]. Spock provides an expressive syntax for writing test cases, based on the Groovy language, and so is a great fit for Grails. It includes a JUnit runner, which means IDE support is effectively universal (any IDE that can run JUnit tests can run Spock tests).
@@ -6,7 +6,7 @@ TIP: Spock is a rich framework (even outside of Grails applications) and well wo
Grails tests are stored (by convention) in the `src/test/groovy` directory (unit tests) and `src/integration-test/groovy` directory (integration/functional tests).
-You can run your Grails tests using the http://docs.grails.org/latest/ref/Command%20Line/test-app.html[`test-app`] command:
+You can run your Grails tests using the https://grails.apache.org/docs/latest/ref/Command%20Line/test-app.html[`test-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v4/guide/urlMappings.adoc b/guides/creating-your-first-grails-app/v4/guide/urlMappings.adoc
index 7c503a00541..b3402af8bf0 100644
--- a/guides/creating-your-first-grails-app/v4/guide/urlMappings.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/urlMappings.adoc
@@ -2,7 +2,7 @@ Now that we have our new "home" page, it would be nice if it was the app's landi
Grails uses the `UrlMappings.groovy` file to route request to the proper controller and action. They can be as simple as URI strings that redirect to a controller and/or action, or they can include wildcards and constraints and become quite sophisticated.
-TIP: Learn much more about URL Mappings from the http://docs.grails.org/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
+TIP: Learn much more about URL Mappings from the https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
Let's look at the default `URLMappings.groovy` file.
diff --git a/guides/creating-your-first-grails-app/v4/guide/views.adoc b/guides/creating-your-first-grails-app/v4/guide/views.adoc
index 842890913d2..0cf55047563 100644
--- a/guides/creating-your-first-grails-app/v4/guide/views.adoc
+++ b/guides/creating-your-first-grails-app/v4/guide/views.adoc
@@ -1,6 +1,6 @@
Views are the third component of the MVC pattern. Views are responsible for presenting data to the user (which might be a browser page, an API endpoint, or some other sort of consumer). In many apps, views are HTML pages designed to be loaded in a browser. However, it is perfectly reasonable for a "view" to be an XML or JSON document, depending on the type of client requesting the view.
-Grails' primary view technology is http://docs.grails.org/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, the GSP p [...]
+Grails' primary view technology is https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, t [...]
You've already worked with GSP views in this guide, but let's quickly cover the basics.
diff --git a/guides/creating-your-first-grails-app/v6/guide/applicationProfile.adoc b/guides/creating-your-first-grails-app/v6/guide/applicationProfile.adoc
index 90f11eb0f49..f64c01ef7d9 100644
--- a/guides/creating-your-first-grails-app/v6/guide/applicationProfile.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/applicationProfile.adoc
@@ -1,7 +1,7 @@
-You can optionally specify a http://docs.grails.org/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
+You can optionally specify a https://grails.apache.org/docs/latest/guide/profiles.html[Profile] for your Grails app. Profiles are available for many common application types, including `rest-api`, `angular`, `react`, and others, and you can even create your own.
-To view of a list of what profiles are available, use the http://docs.grails.org/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
+To view of a list of what profiles are available, use the https://grails.apache.org/docs/latest/ref/Command%20Line/list-profiles.html[`list-profiles`] command.
[source, bash]
----
@@ -36,7 +36,7 @@ You may optionally specify a package and version (defaults to `org.grails.profil
grails create-app myApp -profile org.grails.profiles:react:1.0.2
----
-To get detailed information about a profile use the http://docs.grails.org/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
+To get detailed information about a profile use the https://grails.apache.org/docs/latest/ref/Command%20Line/profile-info.html[`profile-info`] command.
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v6/guide/console.adoc b/guides/creating-your-first-grails-app/v6/guide/console.adoc
index 142b2a4da02..d9eab9856fa 100644
--- a/guides/creating-your-first-grails-app/v6/guide/console.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/console.adoc
@@ -1,6 +1,6 @@
-Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the http://docs.grails.org/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
+Right now we don't have any controllers or views set up to play with our domain model. We'll get there shortly, but for now, let's fire up the https://grails.apache.org/docs/latest/ref/Command%20Line/console.html[Grails Console] so we can explore what Grails and GORM have to offer.
-If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
+If the application is still running, shut it down with either kbd:[Ctrl+C], or (if running Grails in https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode], the `stop-app` command).
Launch the Grails Console:
diff --git a/guides/creating-your-first-grails-app/v6/guide/controllers.adoc b/guides/creating-your-first-grails-app/v6/guide/controllers.adoc
index e1006cf534a..177da6e7c61 100644
--- a/guides/creating-your-first-grails-app/v6/guide/controllers.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/controllers.adoc
@@ -1,6 +1,6 @@
This section will focus on the basics of creating a controller and defining actions.
-TIP: While not part of the "MVC" triad, Grails also provides support for http://docs.grails.org/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
+TIP: While not part of the "MVC" triad, Grails also provides support for https://grails.apache.org/docs/latest/guide/single.html#services[services]. In a Grails application of any complexity, it is considered best practice to keep core application logic in services. We'll get to services later on in this guide.
Following the convention over configuration principle, Grails will configure any Groovy classes under `grails-app/controllers/` as controllers, without any additional configuration. You can create the Groovy class yourself, or use the `create-controller` command to generate the controller and an associated test spec.
@@ -27,7 +27,7 @@ class HomeController {
}
----
-Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the http://docs.grails.org/latest/guide/theWebLay [...]
+Grails has created a controller with a single *action*. Actions are public methods in a controller, which can respond to requests. Typically, a controller action will receive a request, obtain some data (optionally using parameters or a body of the request, if present), and render the result to the browser (e.g, as a webpage). Controller actions can also redirect requests, forward, call service methods, and return HTTP response codes. See the https://grails.apache.org/docs/latest/guide/t [...]
We don't have any need for logic in this particular action just yet, but we would like it to render a page. We'll look at GSP pages in more detail in the <<Views>> section, but for now, let's create a very simple GSP page for our `HomeController.index` action to display.
diff --git a/guides/creating-your-first-grails-app/v6/guide/createApp.adoc b/guides/creating-your-first-grails-app/v6/guide/createApp.adoc
index 1e8e61aeeca..b3ca8033f0d 100644
--- a/guides/creating-your-first-grails-app/v6/guide/createApp.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/createApp.adoc
@@ -1,4 +1,4 @@
-Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the http://docs.grails.org/latest/ref/Command%20Line/create-app.html[`create-app`] command:
+Creating a Grails app is about as simple as could be - once you have installed Grails, simply run the https://grails.apache.org/docs/latest/ref/Command%20Line/create-app.html[`create-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v6/guide/creatingDomainClass.adoc b/guides/creating-your-first-grails-app/v6/guide/creatingDomainClass.adoc
index d146c46d7e9..0b9464dcc73 100644
--- a/guides/creating-your-first-grails-app/v6/guide/creatingDomainClass.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/creatingDomainClass.adoc
@@ -44,4 +44,4 @@ class Vehicle {
<1> Properties will be used to create columns in the database (assuming a relational database is used)
<2> Constraints are used to enforce valid data in each field - Grails provides a rich set of constraints for common scenarios, and you can define custom constraints as well
-Please see the Grails documentation for a complete list and documentation of how to use https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://docs.grails.org/latest/ref/Constraints/Usage.html[constraints]
+Please see the Grails documentation for a complete list and documentation of how to use https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[domain classes] and https://grails.apache.org/docs/latest/ref/Constraints/Usage.html[constraints]
diff --git a/guides/creating-your-first-grails-app/v6/guide/deployment.adoc b/guides/creating-your-first-grails-app/v6/guide/deployment.adoc
index a8873526dec..ad0bc77cecc 100644
--- a/guides/creating-your-first-grails-app/v6/guide/deployment.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/deployment.adoc
@@ -11,7 +11,7 @@ BUILD SUCCESSFUL
[TIP]
====
-We didn't cover the topic of http://docs.grails.org/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "production" envi [...]
+We didn't cover the topic of https://grails.apache.org/docs/latest/guide/conf.html[configuration] in this guide (although we did make some edits to our config files), but it's worth mentioning here that Grails supports to concept of Environments, such as "development", "test", and "production". Each environment can have its own config properties and values, so you can have different settings between your development and production systems. By default, the `war` command uses the "producti [...]
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v6/guide/gspLinks.adoc b/guides/creating-your-first-grails-app/v6/guide/gspLinks.adoc
index d2b192b21f5..094cc19c594 100644
--- a/guides/creating-your-first-grails-app/v6/guide/gspLinks.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/gspLinks.adoc
@@ -6,4 +6,4 @@ Let's take a look at one more common GSP tag: `<g:link>`
include::../snippets/grails-app/views/home/index.gsp[indent=0,lines="34..36"]
----
-`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the http://docs.grails.org/latest/ref/Tags/link [...]
+`<g:link>` renders an HTML `<a>` tag, but it has the advantage in that it allows you to specify your link target following Grails conventions, such as this example (using the `controller`, `action` and `id` attributes). `<g:link>` is also smart enough to follow our URL mappings, so if we change the URL mapping for `vehicle/show`, the `<g:link>` tag will still render the correct URL. There's many more attributes supported by `<g:link>` - see the https://grails.apache.org/docs/latest/ref/T [...]
diff --git a/guides/creating-your-first-grails-app/v6/guide/respond.adoc b/guides/creating-your-first-grails-app/v6/guide/respond.adoc
index f2e2bde7fac..4a39af41256 100644
--- a/guides/creating-your-first-grails-app/v6/guide/respond.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/respond.adoc
@@ -22,7 +22,7 @@ class HomeController {
}
----
<1> We're calling the `respond` method to render a Groovy map of content to the requestor, containing a `name` property from the session (defaulting to "User" if no session value exists) and the current total of `Vehicle` instances from GORM's `count` method.
-<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://docs.grails.org/latest/ref/Controllers/session.html[Grails documentation].
+<2> `session` is an instance of the Servlet API’s`HttpSession` class, and is available in every controller. We can retrieve and store properties in the session - in this case, we're storing a `String` with the attribute `name` in the session. For more see the https://grails.apache.org/docs/latest/ref/Controllers/session.html[Grails documentation].
<3> We're using `flash` scope to set a message to display upon the next request
<4> We don't have any specific content to display in this action, so we issue a redirect back to the `index` action (note that in Groovy method parenthesis are optional so long as there is at least one argument).
diff --git a/guides/creating-your-first-grails-app/v6/guide/runningTheApp.adoc b/guides/creating-your-first-grails-app/v6/guide/runningTheApp.adoc
index 076ff536375..97b16910c9a 100644
--- a/guides/creating-your-first-grails-app/v6/guide/runningTheApp.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/runningTheApp.adoc
@@ -1,6 +1,6 @@
Now that you've created (or downloaded) your Grails project, it's time to run it and see what Grails has already given you.
-If you have a local installation of Grails, you can run the app using the http://docs.grails.org/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
+If you have a local installation of Grails, you can run the app using the https://grails.apache.org/docs/latest/ref/Command%20Line/run-app.html[run-app] command from within your project:
[source, bash]
----
@@ -9,7 +9,7 @@ $ cd myApp/
**Run the App without Grails Installed**
-Thanks to the http://docs.grails.org/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
+Thanks to the https://grails.apache.org/docs/latest/guide/introduction.html#whatsNewGrailsWrapper[Grails Wrapper], as of Grails version 3.2.3 or later, you can run any Grails command without having
Grails installed. If you download it from the http://start.grails.org[Grails Application Forge], the Grails Wrapper is included too.
[source, bash]
@@ -28,7 +28,7 @@ $ grails run-app
**Run the App with Grails Interactive Mode**
-You can also use Grails' http://docs.grails.org/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
+You can also use Grails' https://grails.apache.org/docs/latest/guide/commandLine.html#interactiveMode[Interactive Mode] to run the Grails runtime, from which you can issue any Grails command without waiting for the runtime to spin up for each task.
In this guide we will be preferring the Grails wrapper for most commands.
diff --git a/guides/creating-your-first-grails-app/v6/guide/staticScaffolding.adoc b/guides/creating-your-first-grails-app/v6/guide/staticScaffolding.adoc
index 5b0bc4711f5..8d5a03da3a5 100644
--- a/guides/creating-your-first-grails-app/v6/guide/staticScaffolding.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/staticScaffolding.adoc
@@ -39,12 +39,12 @@ Open the `VehicleController.groovy` file at `grails-app/controllers/org/grails/g
include::../snippets/grails-app/controllers/org/grails/guides/scaffolding/VehicleController.groovy[indent=0,lines="4..8,10..114"]
----
-<1> The http://gorm.grails.org/latest/api/grails/gorm/transactions/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the http://docs.grails.org/latest/guide/single.html#declarativeTransactions[Grails documentation]
-<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://docs.grails.org/latest/ref/Controllers/params.html[Grails documentation] for more detail.
-<3> The `respond` method takes an object to return to the requestor, using https://docs.grails.org/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://docs.grails.org/latest/ref/Controllers/respond.ht [...]
-<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://docs.grails.org/latest/ref/Controllers/request.html[Grails documentation on `request`].
-<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://docs.grails.org/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
-<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://docs.grails.org/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
-<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://docs.grails.org/latest/ref/Controllers/render.html[Grails documentation].
+<1> The http://gorm.grails.org/latest/api/grails/gorm/transactions/Transactional.html[`@Transactional`] annotation configures the transactional behavior of the controller or method. Transactions are used to manage persistence and other complicated operations that should be completed together (and potentially rolled-back if any one of the steps fails). For more information on transactions, see the https://grails.apache.org/docs/latest/guide/single.html#declarativeTransactions[Grails docu [...]
+<2> The `params` object is available to all controllers, and contains a map of any URL parameters on the request. You can refer to any parameter by name to retrieve the value: `params.myCustomParameter` will match this URL parameter: `[url]?myCustomParameter=hello`. See the https://grails.apache.org/docs/latest/ref/Controllers/params.html[Grails documentation] for more detail.
+<3> The `respond` method takes an object to return to the requestor, using https://grails.apache.org/docs/latest/guide/theWebLayer.html#contentNegotiation[content negotiation] to choose the correct type (for example, a request's `Accept` header might specify JSON or XML). `respond` also can accept a map of arguments, such as `model` (which defines the way the data is loaded on a page). For more on how to use the `respond` method, see the https://grails.apache.org/docs/latest/ref/Controll [...]
+<4> `request` is available on all controllers, and is an instance of the Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html[HttpServletRequest] class. You can access request headers, store properties in the request scope, and get information about the requestor using this object. For more see the https://grails.apache.org/docs/latest/ref/Controllers/request.html[Grails documentation on `request`].
+<5> `flash` is a map that stores objects within the session for the *next* request, automatically clearing them after that next request completes. This is useful for passing error messages or other data that you want the next request to access. For more, see the https://grails.apache.org/docs/latest/ref/Controllers/flash.html[Grails documentation on `flash`].
+<6> The `redirect` method is a simple one - it allows the action to redirect the request to another action, controller, or a URI. You can also pass along parameters with the redirect. See the https://grails.apache.org/docs/latest/ref/Controllers/redirect.html[Grails documentation on `redirect`] for more.
+<7> The `render` method is a less sophisticated version of `respond` - it doesn't perform content negotiation, so you have to specify exactly what you want to render. You can render plain text, a view or template, an HTTP response code, or any object that has a String representation. See the https://grails.apache.org/docs/latest/ref/Controllers/render.html[Grails documentation].
That's a lot of code! Generating and modifying a scaffold controller is a good learning exercise, so feel free to experiment and modify this code - you can always revert back to the version in the `completed` project of this guide.
diff --git a/guides/creating-your-first-grails-app/v6/guide/testing.adoc b/guides/creating-your-first-grails-app/v6/guide/testing.adoc
index f51123657e2..dd66193bae7 100644
--- a/guides/creating-your-first-grails-app/v6/guide/testing.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/testing.adoc
@@ -1,4 +1,4 @@
-Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. http://docs.grails.org/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. http://docs.grails.org/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up and running, and [...]
+Testing is a vital part of web application development. Grails provides support for three types of testing: unit tests, integration tests, and functional tests. https://grails.apache.org/docs/latest/guide/testing.html#unitTesting[Unit tests] are usually the simplest kind, focusing on a specific piece of code without depending on other parts of your app. https://grails.apache.org/docs/latest/guide/testing.html#integrationTesting[Integration tests] require the Grails environment to be up a [...]
The testing framework used by Grails is http://spockframework.org[Spock]. Spock provides an expressive syntax for writing test cases, based on the Groovy language, and so is a great fit for Grails. It includes a JUnit runner, which means IDE support is effectively universal (any IDE that can run JUnit tests can run Spock tests).
@@ -6,7 +6,7 @@ TIP: Spock is a rich framework (even outside of Grails applications) and well wo
Grails tests are stored (by convention) in the `src/test/groovy` directory (unit tests) and `src/integration-test/groovy` directory (integration/functional tests).
-You can run your Grails tests using the http://docs.grails.org/latest/ref/Command%20Line/test-app.html[`test-app`] command:
+You can run your Grails tests using the https://grails.apache.org/docs/latest/ref/Command%20Line/test-app.html[`test-app`] command:
[source, bash]
----
diff --git a/guides/creating-your-first-grails-app/v6/guide/urlMappings.adoc b/guides/creating-your-first-grails-app/v6/guide/urlMappings.adoc
index 7c503a00541..b3402af8bf0 100644
--- a/guides/creating-your-first-grails-app/v6/guide/urlMappings.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/urlMappings.adoc
@@ -2,7 +2,7 @@ Now that we have our new "home" page, it would be nice if it was the app's landi
Grails uses the `UrlMappings.groovy` file to route request to the proper controller and action. They can be as simple as URI strings that redirect to a controller and/or action, or they can include wildcards and constraints and become quite sophisticated.
-TIP: Learn much more about URL Mappings from the http://docs.grails.org/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
+TIP: Learn much more about URL Mappings from the https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappings[Grails documentation]
Let's look at the default `URLMappings.groovy` file.
diff --git a/guides/creating-your-first-grails-app/v6/guide/views.adoc b/guides/creating-your-first-grails-app/v6/guide/views.adoc
index 842890913d2..0cf55047563 100644
--- a/guides/creating-your-first-grails-app/v6/guide/views.adoc
+++ b/guides/creating-your-first-grails-app/v6/guide/views.adoc
@@ -1,6 +1,6 @@
Views are the third component of the MVC pattern. Views are responsible for presenting data to the user (which might be a browser page, an API endpoint, or some other sort of consumer). In many apps, views are HTML pages designed to be loaded in a browser. However, it is perfectly reasonable for a "view" to be an XML or JSON document, depending on the type of client requesting the view.
-Grails' primary view technology is http://docs.grails.org/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, the GSP p [...]
+Grails' primary view technology is https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Groovy Server Pages]. It follows many of the conventions of JSP and ASP, but naturally it is based upon the Groovy language. GSP pages are essentially HTML documents, but they support a number of special tags (typically prefix with `g:`) to allow programmatic control over your views. You can even write arbitrary Groovy code in your GSP pages, but this is *strongly* discouraged - ideally, t [...]
You've already worked with GSP views in this guide, but let's quickly cover the basics.
diff --git a/guides/gorm-graphql-with-react-and-apollo/v4/guide/conclusion.adoc b/guides/gorm-graphql-with-react-and-apollo/v4/guide/conclusion.adoc
index 8dbecd7d1e8..02cdab4df28 100644
--- a/guides/gorm-graphql-with-react-and-apollo/v4/guide/conclusion.adoc
+++ b/guides/gorm-graphql-with-react-and-apollo/v4/guide/conclusion.adoc
@@ -1 +1 @@
-In this guide we've seen how easy is to create a full-featured GraphQL schema with Grails, and to interact with that schema in a Single-Page-App, using Apollo and the React Profile for Grails. Please refer to the https://grails.github.io/gorm-graphql/latest/guide/index.html[GORM for GraphQL Documentation], and related http://guides.grails.org/categories/grailsreact.html[Grails & React Guides] to learn more.
\ No newline at end of file
+In this guide we've seen how easy is to create a full-featured GraphQL schema with Grails, and to interact with that schema in a Single-Page-App, using Apollo and the React Profile for Grails. Please refer to the https://grails.github.io/gorm-graphql/latest/guide/index.html[GORM for GraphQL Documentation], and related https://grails.apache.org/guides/categories/grailsreact.html[Grails & React Guides] to learn more.
\ No newline at end of file
diff --git a/guides/gorm-graphql-with-react-and-apollo/v4/guide/gettingStarted.adoc b/guides/gorm-graphql-with-react-and-apollo/v4/guide/gettingStarted.adoc
index ef11fcce9b4..f1be888bc4d 100644
--- a/guides/gorm-graphql-with-react-and-apollo/v4/guide/gettingStarted.adoc
+++ b/guides/gorm-graphql-with-react-and-apollo/v4/guide/gettingStarted.adoc
@@ -1,6 +1,6 @@
In this guide you will learn how to leverage GORM's support for GraphQL. You will configure Grails to act as a GraphQL server,
-The `initial` sample project already has a simple conference-related REST API (consisting of two domain classes, `Speaker` and `Talk`) configured using the http://docs.grails.org/latest/guide/single.html#domainResources[@Resource annotation]. The project is using the https://grails-profiles.github.io/react/latest/guide/index.html[react profile], and a simple React app has been provided which will list out the speakers, as well as the talks belonging to each speaker.
+The `initial` sample project already has a simple conference-related REST API (consisting of two domain classes, `Speaker` and `Talk`) configured using the https://grails.apache.org/docs/latest/guide/single.html#domainResources[@Resource annotation]. The project is using the https://grails-profiles.github.io/react/latest/guide/index.html[react profile], and a simple React app has been provided which will list out the speakers, as well as the talks belonging to each speaker.
The React app is quite trivial and naively uses the default REST API provided by Grails - e.g, the app makes one REST call to list the speakers, and then iterates over the talk ids for each speaker, making a separate REST call to get the details for each talk. This means that a single load of the app can require many REST calls simply to acquire the data needed to render the app.
@@ -14,7 +14,7 @@ http://localhost:8080/talk/5 200 fetch 293 B 284 ms
```
-Of course there are a few ways we could resolve this problem using standard REST techniques, including hypermedia, or customized endpoints (using http://views.grails.org[JSON Views], for example) - however in more complex apps it is possible that this could lead to a proliferation of custom endpoints providing different combinations of data. In addition, some endpoints might provide more data than the app actually requires - there is no way to express the desired "piece" of data in a ty [...]
+Of course there are a few ways we could resolve this problem using standard REST techniques, including hypermedia, or customized endpoints (using https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views], for example) - however in more complex apps it is possible that this could lead to a proliferation of custom endpoints providing different combinations of data. In addition, some endpoints might provide more data than the app actually requires - there is no way to e [...]
This is where GraphQL shines - it allows consumers of our API, whether private clients (like our own Single-Page Applications) or public users, to specify the exact pieces of data that they need, in a declarative way. GraphQL queries can even be https://dev-blog.apollodata.com/a-stronger-typed-react-apollo-c43bd52be0d8[codifed as Flow types], making the data requirements of your components explicit and testable.
diff --git a/guides/grails-async-promises/v3/guide/initial.adoc b/guides/grails-async-promises/v3/guide/initial.adoc
index dcf59eb7b64..8efc6705741 100644
--- a/guides/grails-async-promises/v3/guide/initial.adoc
+++ b/guides/grails-async-promises/v3/guide/initial.adoc
@@ -1,4 +1,4 @@
-The _initial_ folder contains the sample Grails application developed during the Grails Guide: http://guides.grails.org/grails-mock-http-server/guide/index.html[Consume and test a third-party REST API].
+The _initial_ folder contains the sample Grails application developed during the Grails Guide: https://grails.apache.org/guides/grails-mock-http-server/guide/index.html[Consume and test a third-party REST API].
It contains code to invoke the https://openweathermap.org/api[Open Weather Map API] to retrieve the weather forecast for a city.
diff --git a/guides/grails-async-promises/v3/guide/writingTheApp.adoc b/guides/grails-async-promises/v3/guide/writingTheApp.adoc
index 598bdd734de..60ee4ce2346 100644
--- a/guides/grails-async-promises/v3/guide/writingTheApp.adoc
+++ b/guides/grails-async-promises/v3/guide/writingTheApp.adoc
@@ -9,4 +9,4 @@ Your project already contains the async dependency:
include::{sourcedir}/build.gradle[tag=async]
----
-Grails Async capabilites documentation can be found in http://async.grails.org[async.grails.org].
\ No newline at end of file
+Grails Async capabilites documentation can be found in https://grails.apache.org/docs/latest/guide/async.html[async.grails.org].
\ No newline at end of file
diff --git a/guides/grails-async-promises/v4/guide/initial.adoc b/guides/grails-async-promises/v4/guide/initial.adoc
index 51176f2b2cf..88f857c12f0 100644
--- a/guides/grails-async-promises/v4/guide/initial.adoc
+++ b/guides/grails-async-promises/v4/guide/initial.adoc
@@ -1,4 +1,4 @@
-The _initial_ folder contains the sample Grails application developed during the Grails Guide: http://guides.grails.org/grails-mock-http-server/guide/index.html[Consume and test a third-party REST API].
+The _initial_ folder contains the sample Grails application developed during the Grails Guide: https://grails.apache.org/guides/grails-mock-http-server/guide/index.html[Consume and test a third-party REST API].
It contains code to invoke the https://openweathermap.org/api[Open Weather Map API] to retrieve the weather forecast for a city.
diff --git a/guides/grails-async-promises/v4/guide/writingTheApp.adoc b/guides/grails-async-promises/v4/guide/writingTheApp.adoc
index 598bdd734de..60ee4ce2346 100644
--- a/guides/grails-async-promises/v4/guide/writingTheApp.adoc
+++ b/guides/grails-async-promises/v4/guide/writingTheApp.adoc
@@ -9,4 +9,4 @@ Your project already contains the async dependency:
include::{sourcedir}/build.gradle[tag=async]
----
-Grails Async capabilites documentation can be found in http://async.grails.org[async.grails.org].
\ No newline at end of file
+Grails Async capabilites documentation can be found in https://grails.apache.org/docs/latest/guide/async.html[async.grails.org].
\ No newline at end of file
diff --git a/guides/grails-basicauth/v3/guide/writingTheApp/views.adoc b/guides/grails-basicauth/v3/guide/writingTheApp/views.adoc
index 6ea96205fcb..b4f8a3f65e2 100644
--- a/guides/grails-basicauth/v3/guide/writingTheApp/views.adoc
+++ b/guides/grails-basicauth/v3/guide/writingTheApp/views.adoc
@@ -1,4 +1,4 @@
-Render the controller output as a JSON Payload with the aid of http://views.grails.org[JSON Views].
+Render the controller output as a JSON Payload with the aid of https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views].
[source,groovy]
.grails-app/views/home/index.gson
----
diff --git a/guides/grails-basicauth/v4/guide/writingTheApp/views.adoc b/guides/grails-basicauth/v4/guide/writingTheApp/views.adoc
index 6ea96205fcb..b4f8a3f65e2 100644
--- a/guides/grails-basicauth/v4/guide/writingTheApp/views.adoc
+++ b/guides/grails-basicauth/v4/guide/writingTheApp/views.adoc
@@ -1,4 +1,4 @@
-Render the controller output as a JSON Payload with the aid of http://views.grails.org[JSON Views].
+Render the controller output as a JSON Payload with the aid of https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views].
[source,groovy]
.grails-app/views/home/index.gson
----
diff --git a/guides/grails-codenarc/v4/guide/multiproject.adoc b/guides/grails-codenarc/v4/guide/multiproject.adoc
index 8452a6a3cdd..c7d679e3bfa 100644
--- a/guides/grails-codenarc/v4/guide/multiproject.adoc
+++ b/guides/grails-codenarc/v4/guide/multiproject.adoc
@@ -3,4 +3,4 @@ CodeNarc Rule as shown in the next image:
image::multiproject.png[]
-Check our http://guides.grails.org/grails-multi-project-build/guide/index.html[Grails Multi-Project Build] Guide, to learn more.
+Check our https://grails.apache.org/guides/grails-multi-project-build/guide/index.html[Grails Multi-Project Build] Guide, to learn more.
diff --git a/guides/grails-configuration-properties-micronaut/v4/guide/writingTheApp/taglib.adoc b/guides/grails-configuration-properties-micronaut/v4/guide/writingTheApp/taglib.adoc
index d256471fad3..6085f74dca6 100644
--- a/guides/grails-configuration-properties-micronaut/v4/guide/writingTheApp/taglib.adoc
+++ b/guides/grails-configuration-properties-micronaut/v4/guide/writingTheApp/taglib.adoc
@@ -1,4 +1,4 @@
-Create a https://gsp.grails.org/latest/guide/index.html#taglibs[Tag Library] to render the address:
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Tag Library] to render the address:
[source, groovy]
.grails-app/taglib/example/grails/AddressTagLib.groovy
diff --git a/guides/grails-configuration-properties-micronaut/v6/guide/writingTheApp/taglib.adoc b/guides/grails-configuration-properties-micronaut/v6/guide/writingTheApp/taglib.adoc
index d256471fad3..6085f74dca6 100644
--- a/guides/grails-configuration-properties-micronaut/v6/guide/writingTheApp/taglib.adoc
+++ b/guides/grails-configuration-properties-micronaut/v6/guide/writingTheApp/taglib.adoc
@@ -1,4 +1,4 @@
-Create a https://gsp.grails.org/latest/guide/index.html#taglibs[Tag Library] to render the address:
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Tag Library] to render the address:
[source, groovy]
.grails-app/taglib/example/grails/AddressTagLib.groovy
diff --git a/guides/grails-configuration-properties/v3/guide/writingTheApp/taglib.adoc b/guides/grails-configuration-properties/v3/guide/writingTheApp/taglib.adoc
index 5fcfe272361..bbabb0e6bdc 100644
--- a/guides/grails-configuration-properties/v3/guide/writingTheApp/taglib.adoc
+++ b/guides/grails-configuration-properties/v3/guide/writingTheApp/taglib.adoc
@@ -1,4 +1,4 @@
-Create a https://gsp.grails.org/latest/guide/index.html#taglibs[Tag Library] to render the address:
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Tag Library] to render the address:
[source, groovy]
.grails-app/taglib/example/grails/AddressTagLib.groovy
diff --git a/guides/grails-configuration-properties/v4/guide/writingTheApp/taglib.adoc b/guides/grails-configuration-properties/v4/guide/writingTheApp/taglib.adoc
index 5fcfe272361..bbabb0e6bdc 100644
--- a/guides/grails-configuration-properties/v4/guide/writingTheApp/taglib.adoc
+++ b/guides/grails-configuration-properties/v4/guide/writingTheApp/taglib.adoc
@@ -1,4 +1,4 @@
-Create a https://gsp.grails.org/latest/guide/index.html#taglibs[Tag Library] to render the address:
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[Tag Library] to render the address:
[source, groovy]
.grails-app/taglib/example/grails/AddressTagLib.groovy
diff --git a/guides/grails-controller-testing/v3/guide/domainClassAndScaffold.adoc b/guides/grails-controller-testing/v3/guide/domainClassAndScaffold.adoc
index e9b2f2ad4dc..bd9f4c5a151 100644
--- a/guides/grails-controller-testing/v3/guide/domainClassAndScaffold.adoc
+++ b/guides/grails-controller-testing/v3/guide/domainClassAndScaffold.adoc
@@ -24,4 +24,4 @@ Delete this file:
$ src/test/groovy/demo/StudentSpec.groovy
----
-Learn more about testing domain classes in the http://guides.grails.org/grails-test-domain-class-constraints/guide/index.html[How to test Domain Class constraints?] Guide.
+Learn more about testing domain classes in the https://grails.apache.org/guides/grails-test-domain-class-constraints/guide/index.html[How to test Domain Class constraints?] Guide.
diff --git a/guides/grails-controller-testing/v3/guide/unitTestSave.adoc b/guides/grails-controller-testing/v3/guide/unitTestSave.adoc
index 69b0f5b2ce8..b195a8dfcae 100644
--- a/guides/grails-controller-testing/v3/guide/unitTestSave.adoc
+++ b/guides/grails-controller-testing/v3/guide/unitTestSave.adoc
@@ -1,6 +1,6 @@
The `save()` action method use a command object as a parameter.
-Check the guide http://guides.grails.org/command-objects-and-forms/guide/index.html[Using Command Objects to handle form data] to learn more about command objects.
+Check the guide https://grails.apache.org/guides/command-objects-and-forms/guide/index.html[Using Command Objects to handle form data] to learn more about command objects.
[source, groovy]
.grails-app/controllers/demo/StudentSaveCommand.groovy
diff --git a/guides/grails-controller-testing/v4/guide/domainClassAndScaffold.adoc b/guides/grails-controller-testing/v4/guide/domainClassAndScaffold.adoc
index e9b2f2ad4dc..bd9f4c5a151 100644
--- a/guides/grails-controller-testing/v4/guide/domainClassAndScaffold.adoc
+++ b/guides/grails-controller-testing/v4/guide/domainClassAndScaffold.adoc
@@ -24,4 +24,4 @@ Delete this file:
$ src/test/groovy/demo/StudentSpec.groovy
----
-Learn more about testing domain classes in the http://guides.grails.org/grails-test-domain-class-constraints/guide/index.html[How to test Domain Class constraints?] Guide.
+Learn more about testing domain classes in the https://grails.apache.org/guides/grails-test-domain-class-constraints/guide/index.html[How to test Domain Class constraints?] Guide.
diff --git a/guides/grails-controller-testing/v4/guide/unitTestSave.adoc b/guides/grails-controller-testing/v4/guide/unitTestSave.adoc
index 69b0f5b2ce8..b195a8dfcae 100644
--- a/guides/grails-controller-testing/v4/guide/unitTestSave.adoc
+++ b/guides/grails-controller-testing/v4/guide/unitTestSave.adoc
@@ -1,6 +1,6 @@
The `save()` action method use a command object as a parameter.
-Check the guide http://guides.grails.org/command-objects-and-forms/guide/index.html[Using Command Objects to handle form data] to learn more about command objects.
+Check the guide https://grails.apache.org/guides/command-objects-and-forms/guide/index.html[Using Command Objects to handle form data] to learn more about command objects.
[source, groovy]
.grails-app/controllers/demo/StudentSaveCommand.groovy
diff --git a/guides/grails-custom-security-tenant-resolver/v3/guide/controller.adoc b/guides/grails-custom-security-tenant-resolver/v3/guide/controller.adoc
index f828357fab1..b78a995cc95 100644
--- a/guides/grails-custom-security-tenant-resolver/v3/guide/controller.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v3/guide/controller.adoc
@@ -6,7 +6,7 @@ Create a simple controller which uses with the previously defined `PlanService`
include::../snippets/grails-app/controllers/demo/PlanController.groovy[]
----
-We render the `Plan` instances as JSON with the help of http://views.grails.org[JSON Views]
+We render the `Plan` instances as JSON with the help of https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views]
[source,groovy]
.grails-app/views/plan/index.gson
diff --git a/guides/grails-custom-security-tenant-resolver/v3/guide/security.adoc b/guides/grails-custom-security-tenant-resolver/v3/guide/security.adoc
index ee1a6ddc099..23206bca09d 100644
--- a/guides/grails-custom-security-tenant-resolver/v3/guide/security.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v3/guide/security.adoc
@@ -14,7 +14,7 @@ include::../snippets/grails-app/domain/demo/Role.groovy[]
Create a class `UserPasswordEncoderListener` which deals with the User's password encoding.
-It uses the `@Listener` annotation to listen *synchronously* to https://async.grails.org/latest/guide/index.html#gormEvents[Events from GORM].
+It uses the `@Listener` annotation to listen *synchronously* to https://grails.apache.org/docs/latest/guide/async.html[Events from GORM].
[source,groovy]
.src/main/groovy/demo/UserPasswordEncoderListener.groovy
diff --git a/guides/grails-custom-security-tenant-resolver/v3/guide/writingTheApp.adoc b/guides/grails-custom-security-tenant-resolver/v3/guide/writingTheApp.adoc
index 283914d4fa6..7a56f3e5962 100644
--- a/guides/grails-custom-security-tenant-resolver/v3/guide/writingTheApp.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v3/guide/writingTheApp.adoc
@@ -1 +1 @@
-NOTE: This guide uses Multi-Tenancy DISCRIMINATOR mode. To learn more, read http://guides.grails.org/discriminator-per-tenant/guide/index.html[Single Database Multi-Tenancy Discriminator Column] Guide.
\ No newline at end of file
+NOTE: This guide uses Multi-Tenancy DISCRIMINATOR mode. To learn more, read https://grails.apache.org/guides/discriminator-per-tenant/guide/index.html[Single Database Multi-Tenancy Discriminator Column] Guide.
\ No newline at end of file
diff --git a/guides/grails-custom-security-tenant-resolver/v4/guide/controller.adoc b/guides/grails-custom-security-tenant-resolver/v4/guide/controller.adoc
index f828357fab1..b78a995cc95 100644
--- a/guides/grails-custom-security-tenant-resolver/v4/guide/controller.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v4/guide/controller.adoc
@@ -6,7 +6,7 @@ Create a simple controller which uses with the previously defined `PlanService`
include::../snippets/grails-app/controllers/demo/PlanController.groovy[]
----
-We render the `Plan` instances as JSON with the help of http://views.grails.org[JSON Views]
+We render the `Plan` instances as JSON with the help of https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views]
[source,groovy]
.grails-app/views/plan/index.gson
diff --git a/guides/grails-custom-security-tenant-resolver/v4/guide/security.adoc b/guides/grails-custom-security-tenant-resolver/v4/guide/security.adoc
index ee1a6ddc099..23206bca09d 100644
--- a/guides/grails-custom-security-tenant-resolver/v4/guide/security.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v4/guide/security.adoc
@@ -14,7 +14,7 @@ include::../snippets/grails-app/domain/demo/Role.groovy[]
Create a class `UserPasswordEncoderListener` which deals with the User's password encoding.
-It uses the `@Listener` annotation to listen *synchronously* to https://async.grails.org/latest/guide/index.html#gormEvents[Events from GORM].
+It uses the `@Listener` annotation to listen *synchronously* to https://grails.apache.org/docs/latest/guide/async.html[Events from GORM].
[source,groovy]
.src/main/groovy/demo/UserPasswordEncoderListener.groovy
diff --git a/guides/grails-custom-security-tenant-resolver/v4/guide/writingTheApp.adoc b/guides/grails-custom-security-tenant-resolver/v4/guide/writingTheApp.adoc
index 283914d4fa6..7a56f3e5962 100644
--- a/guides/grails-custom-security-tenant-resolver/v4/guide/writingTheApp.adoc
+++ b/guides/grails-custom-security-tenant-resolver/v4/guide/writingTheApp.adoc
@@ -1 +1 @@
-NOTE: This guide uses Multi-Tenancy DISCRIMINATOR mode. To learn more, read http://guides.grails.org/discriminator-per-tenant/guide/index.html[Single Database Multi-Tenancy Discriminator Column] Guide.
\ No newline at end of file
+NOTE: This guide uses Multi-Tenancy DISCRIMINATOR mode. To learn more, read https://grails.apache.org/guides/discriminator-per-tenant/guide/index.html[Single Database Multi-Tenancy Discriminator Column] Guide.
\ No newline at end of file
diff --git a/guides/grails-dynamic-multiple-datasources/v3/guide/configuration.adoc b/guides/grails-dynamic-multiple-datasources/v3/guide/configuration.adoc
index e06bb5d50b0..bac9e1fa75e 100644
--- a/guides/grails-dynamic-multiple-datasources/v3/guide/configuration.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v3/guide/configuration.adoc
@@ -34,4 +34,4 @@ include::../snippets/grails-app/conf/application.yml[tag=multiTenancyConfigurati
----
<1> Define Multi-Tenancy mode as `DATABASE`
-<2> Set the Tenant Resolver class to a custom class which you wrote in the http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html[Custom Tenant Resolver by JWT] guide.
+<2> Set the Tenant Resolver class to a custom class which you wrote in the https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html[Custom Tenant Resolver by JWT] guide.
diff --git a/guides/grails-dynamic-multiple-datasources/v3/guide/gettingStarted.adoc b/guides/grails-dynamic-multiple-datasources/v3/guide/gettingStarted.adoc
index 347d85b827f..a9d7d8d875e 100644
--- a/guides/grails-dynamic-multiple-datasources/v3/guide/gettingStarted.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v3/guide/gettingStarted.adoc
@@ -1,2 +1,2 @@
-This guide starts where the http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] left off.
+This guide starts where the https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] left off.
Please, complete that guide before starting this guide to get a better understanding.
\ No newline at end of file
diff --git a/guides/grails-dynamic-multiple-datasources/v3/guide/gormevents.adoc b/guides/grails-dynamic-multiple-datasources/v3/guide/gormevents.adoc
index 816ac6a63a9..0d5a00b87a6 100644
--- a/guides/grails-dynamic-multiple-datasources/v3/guide/gormevents.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v3/guide/gormevents.adoc
@@ -1,6 +1,6 @@
Create a class named `UserInsertedListener`. It creates a new connection source when a new user is inserted.
-It uses the `@Listener` annotation to listen *synchronously* to https://async.grails.org/latest/guide/index.html#gormEvents[Events from GORM].
+It uses the `@Listener` annotation to listen *synchronously* to https://grails.apache.org/docs/latest/guide/async.html[Events from GORM].
[source,groovy]
.src/main/groovy/demo/UserInsertedListener.groovy
diff --git a/guides/grails-dynamic-multiple-datasources/v3/guide/test.adoc b/guides/grails-dynamic-multiple-datasources/v3/guide/test.adoc
index 044b2f8fa82..baa9d12033b 100644
--- a/guides/grails-dynamic-multiple-datasources/v3/guide/test.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v3/guide/test.adoc
@@ -1,4 +1,4 @@
-We have modified slightly the functional test of http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] Guide to verify
+We have modified slightly the functional test of https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] Guide to verify
that a new connection source is created when a new `User` is inserted.
[source,groovy]
diff --git a/guides/grails-dynamic-multiple-datasources/v3/guide/writingTheApp.adoc b/guides/grails-dynamic-multiple-datasources/v3/guide/writingTheApp.adoc
index d30597fb3eb..66fc21a302a 100644
--- a/guides/grails-dynamic-multiple-datasources/v3/guide/writingTheApp.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v3/guide/writingTheApp.adoc
@@ -1,4 +1,4 @@
-NOTE: This guide uses Multi-Tenancy DATABASE mode. To learn more, read http://guides.grails.org/database-per-tenant/guide/index.html[Database per Tenant Multi-Tenancy] Guide.
+NOTE: This guide uses Multi-Tenancy DATABASE mode. To learn more, read https://grails.apache.org/guides/database-per-tenant/guide/index.html[Database per Tenant Multi-Tenancy] Guide.
This guides shows a typical flow you will see when creating a SaaS ( Software as a Service ) application using Multi-Tenancy `DATABASE` mode.
diff --git a/guides/grails-dynamic-multiple-datasources/v4/guide/configuration.adoc b/guides/grails-dynamic-multiple-datasources/v4/guide/configuration.adoc
index e06bb5d50b0..bac9e1fa75e 100644
--- a/guides/grails-dynamic-multiple-datasources/v4/guide/configuration.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v4/guide/configuration.adoc
@@ -34,4 +34,4 @@ include::../snippets/grails-app/conf/application.yml[tag=multiTenancyConfigurati
----
<1> Define Multi-Tenancy mode as `DATABASE`
-<2> Set the Tenant Resolver class to a custom class which you wrote in the http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html[Custom Tenant Resolver by JWT] guide.
+<2> Set the Tenant Resolver class to a custom class which you wrote in the https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html[Custom Tenant Resolver by JWT] guide.
diff --git a/guides/grails-dynamic-multiple-datasources/v4/guide/gettingStarted.adoc b/guides/grails-dynamic-multiple-datasources/v4/guide/gettingStarted.adoc
index 347d85b827f..a9d7d8d875e 100644
--- a/guides/grails-dynamic-multiple-datasources/v4/guide/gettingStarted.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v4/guide/gettingStarted.adoc
@@ -1,2 +1,2 @@
-This guide starts where the http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] left off.
+This guide starts where the https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] left off.
Please, complete that guide before starting this guide to get a better understanding.
\ No newline at end of file
diff --git a/guides/grails-dynamic-multiple-datasources/v4/guide/gormevents.adoc b/guides/grails-dynamic-multiple-datasources/v4/guide/gormevents.adoc
index 816ac6a63a9..0d5a00b87a6 100644
--- a/guides/grails-dynamic-multiple-datasources/v4/guide/gormevents.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v4/guide/gormevents.adoc
@@ -1,6 +1,6 @@
Create a class named `UserInsertedListener`. It creates a new connection source when a new user is inserted.
-It uses the `@Listener` annotation to listen *synchronously* to https://async.grails.org/latest/guide/index.html#gormEvents[Events from GORM].
+It uses the `@Listener` annotation to listen *synchronously* to https://grails.apache.org/docs/latest/guide/async.html[Events from GORM].
[source,groovy]
.src/main/groovy/demo/UserInsertedListener.groovy
diff --git a/guides/grails-dynamic-multiple-datasources/v4/guide/test.adoc b/guides/grails-dynamic-multiple-datasources/v4/guide/test.adoc
index 044b2f8fa82..baa9d12033b 100644
--- a/guides/grails-dynamic-multiple-datasources/v4/guide/test.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v4/guide/test.adoc
@@ -1,4 +1,4 @@
-We have modified slightly the functional test of http://guides.grails.org/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] Guide to verify
+We have modified slightly the functional test of https://grails.apache.org/guides/grails-custom-security-tenant-resolver/guide/index.html#test[Custom Tenant Resolver by JWT] Guide to verify
that a new connection source is created when a new `User` is inserted.
[source,groovy]
diff --git a/guides/grails-dynamic-multiple-datasources/v4/guide/writingTheApp.adoc b/guides/grails-dynamic-multiple-datasources/v4/guide/writingTheApp.adoc
index 6ea7372b381..fef06aca729 100644
--- a/guides/grails-dynamic-multiple-datasources/v4/guide/writingTheApp.adoc
+++ b/guides/grails-dynamic-multiple-datasources/v4/guide/writingTheApp.adoc
@@ -1,4 +1,4 @@
-NOTE: This guide uses Multi-Tenancy DATABASE mode. To learn more, read http://guides.grails.org/database-per-tenant/guide/index.html[Database per Tenant Multi-Tenancy] Guide.
+NOTE: This guide uses Multi-Tenancy DATABASE mode. To learn more, read https://grails.apache.org/guides/database-per-tenant/guide/index.html[Database per Tenant Multi-Tenancy] Guide.
This guides shows a typical flow you will see when creating a SaaS ( Software as a Service ) application using Multi-Tenancy `DATABASE` mode.
diff --git a/guides/grails-elasticbeanstalk/v4/guide/nextSteps.adoc b/guides/grails-elasticbeanstalk/v4/guide/nextSteps.adoc
index 501d2a0399d..b7a1f9996c1 100644
--- a/guides/grails-elasticbeanstalk/v4/guide/nextSteps.adoc
+++ b/guides/grails-elasticbeanstalk/v4/guide/nextSteps.adoc
@@ -1,3 +1,3 @@
Grails 3 apps are Spring Boot apps. Read https://aws.amazon.com/blogs/devops/deploying-a-spring-boot-application-on-aws-using-aws-elastic-beanstalk/[Deploying a Spring Boot Application on AWS Using AWS Elastic Beanstalk] tutorial to learn more.
-Explore more features with http://guides.grails.org[Grails Guides].
\ No newline at end of file
+Explore more features with https://grails.apache.org/guides[Grails Guides].
\ No newline at end of file
diff --git a/guides/grails-email/v3/guide/writingTheApp/controller.adoc b/guides/grails-email/v3/guide/writingTheApp/controller.adoc
index 6ee27811357..9e90123a19d 100644
--- a/guides/grails-email/v3/guide/writingTheApp/controller.adoc
+++ b/guides/grails-email/v3/guide/writingTheApp/controller.adoc
@@ -24,7 +24,7 @@ Create `MailController` which use a collaborator, `emailService` to send and ema
include::../../snippets/grails-app/controllers/example/grails/MailController.groovy[]
----
-The previous controller uses a http://docs.grails.org/snapshot/guide/single.html#commandObjects[command object]:
+The previous controller uses a https://grails.apache.org/docs/snapshot/guide/single.html#commandObjects[command object]:
[source,groovy]
.grails-app/controllers/example/grails/EmailCmd.groovy
diff --git a/guides/grails-email/v3/guide/writingTheApp/resources.adoc b/guides/grails-email/v3/guide/writingTheApp/resources.adoc
index dd2c9c3aea0..b2bb6156b5d 100644
--- a/guides/grails-email/v3/guide/writingTheApp/resources.adoc
+++ b/guides/grails-email/v3/guide/writingTheApp/resources.adoc
@@ -1,6 +1,6 @@
Grails integrates with and builds on the http://spring.io/[Spring Framework].
-You can easily register new (or override existing) beans by configuring them in `grails-app/conf/spring/resources.groovy` which uses the http://docs.grails.org/snapshot/guide/single.html#springdsl[Grails Spring DSL].
+You can easily register new (or override existing) beans by configuring them in `grails-app/conf/spring/resources.groovy` which uses the https://grails.apache.org/docs/snapshot/guide/single.html#springdsl[Grails Spring DSL].
Depending on the presence of the required system properties we are going to enable SendGrid or AWS SES integration.
diff --git a/guides/grails-email/v3/guide/writingTheApp/services/awsSesService.adoc b/guides/grails-email/v3/guide/writingTheApp/services/awsSesService.adoc
index 25ed4c0e9fc..978b40b04e0 100644
--- a/guides/grails-email/v3/guide/writingTheApp/services/awsSesService.adoc
+++ b/guides/grails-email/v3/guide/writingTheApp/services/awsSesService.adoc
@@ -2,7 +2,7 @@ ____
Amazon Simple Email Service (Amazon SES) is a cloud-based email sending service designed to help digital marketers and application developers send marketing, notification, and transactional emails. It is a reliable, cost-effective service for businesses of all sizes that use email to keep in contact with their customers.
____
-There is a http://plugins.grails.org/plugin/agorapulse/aws-sdk-ses[AWS SDK SES Grails plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
+There is a https://grails.apache.org/plugins.html[AWS SDK SES Grails plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
Add a dependency to AWS SES SDK:
diff --git a/guides/grails-email/v3/guide/writingTheApp/services/sendGridService.adoc b/guides/grails-email/v3/guide/writingTheApp/services/sendGridService.adoc
index fddb6e21746..e5fdeedc89c 100644
--- a/guides/grails-email/v3/guide/writingTheApp/services/sendGridService.adoc
+++ b/guides/grails-email/v3/guide/writingTheApp/services/sendGridService.adoc
@@ -4,7 +4,7 @@ ____
SendGrid is responsible for sending billions of emails for some of the best and brightest companies in the world.
____
-There is a http://plugins.grails.org/plugin/desirable-objects/grails-sendgrid[SendGrid Grails Plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
+There is a https://grails.apache.org/plugins.html[SendGrid Grails Plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
Add a dependency to SendGrid SDK:
diff --git a/guides/grails-email/v4/guide/writingTheApp/controller.adoc b/guides/grails-email/v4/guide/writingTheApp/controller.adoc
index 6ee27811357..9e90123a19d 100644
--- a/guides/grails-email/v4/guide/writingTheApp/controller.adoc
+++ b/guides/grails-email/v4/guide/writingTheApp/controller.adoc
@@ -24,7 +24,7 @@ Create `MailController` which use a collaborator, `emailService` to send and ema
include::../../snippets/grails-app/controllers/example/grails/MailController.groovy[]
----
-The previous controller uses a http://docs.grails.org/snapshot/guide/single.html#commandObjects[command object]:
+The previous controller uses a https://grails.apache.org/docs/snapshot/guide/single.html#commandObjects[command object]:
[source,groovy]
.grails-app/controllers/example/grails/EmailCmd.groovy
diff --git a/guides/grails-email/v4/guide/writingTheApp/resources.adoc b/guides/grails-email/v4/guide/writingTheApp/resources.adoc
index 7273e6caee6..65c818d9400 100644
--- a/guides/grails-email/v4/guide/writingTheApp/resources.adoc
+++ b/guides/grails-email/v4/guide/writingTheApp/resources.adoc
@@ -1,6 +1,6 @@
Grails integrates with and builds on the http://spring.io/[Spring Framework].
-You can easily register new (or override existing) beans by configuring them in `grails-app/conf/spring/resources.groovy` which uses the http://docs.grails.org/snapshot/guide/single.html#springdsl[Grails Spring DSL].
+You can easily register new (or override existing) beans by configuring them in `grails-app/conf/spring/resources.groovy` which uses the https://grails.apache.org/docs/snapshot/guide/single.html#springdsl[Grails Spring DSL].
Depending on the presence of the required system properties we are going to enable SendGrid or AWS SES integration.
diff --git a/guides/grails-email/v4/guide/writingTheApp/services/awsSesService.adoc b/guides/grails-email/v4/guide/writingTheApp/services/awsSesService.adoc
index b2024bbf71f..5a8238ab362 100644
--- a/guides/grails-email/v4/guide/writingTheApp/services/awsSesService.adoc
+++ b/guides/grails-email/v4/guide/writingTheApp/services/awsSesService.adoc
@@ -2,7 +2,7 @@ ____
Amazon Simple Email Service (Amazon SES) is a cloud-based email sending service designed to help digital marketers and application developers send marketing, notification, and transactional emails. It is a reliable, cost-effective service for businesses of all sizes that use email to keep in contact with their customers.
____
-There is a http://plugins.grails.org/plugin/agorapulse/aws-sdk-ses[AWS SDK SES Grails plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
+There is a https://grails.apache.org/plugins.html[AWS SDK SES Grails plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
Add a dependency to AWS SES SDK:
diff --git a/guides/grails-email/v4/guide/writingTheApp/services/sendGridService.adoc b/guides/grails-email/v4/guide/writingTheApp/services/sendGridService.adoc
index fddb6e21746..e5fdeedc89c 100644
--- a/guides/grails-email/v4/guide/writingTheApp/services/sendGridService.adoc
+++ b/guides/grails-email/v4/guide/writingTheApp/services/sendGridService.adoc
@@ -4,7 +4,7 @@ ____
SendGrid is responsible for sending billions of emails for some of the best and brightest companies in the world.
____
-There is a http://plugins.grails.org/plugin/desirable-objects/grails-sendgrid[SendGrid Grails Plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
+There is a https://grails.apache.org/plugins.html[SendGrid Grails Plugin]. However, in this guide we are going to integrate AWS SDK SES directly.
Add a dependency to SendGrid SDK:
diff --git a/guides/grails-events/v3/guide/gettingStarted.adoc b/guides/grails-events/v3/guide/gettingStarted.adoc
index 00b102bacab..db4b0b8849d 100644
--- a/guides/grails-events/v3/guide/gettingStarted.adoc
+++ b/guides/grails-events/v3/guide/gettingStarted.adoc
@@ -1,2 +1,2 @@
-In this guide, you are going to use https://async.grails.org/latest/guide/index.html#events[Grails Events] to handle a common scenario. A user registers in an application and the app sends the user a welcome email. For example, asking him to verify his email address.
+In this guide, you are going to use https://grails.apache.org/docs/latest/guide/async.html[Grails Events] to handle a common scenario. A user registers in an application and the app sends the user a welcome email. For example, asking him to verify his email address.
We are going to trigger the Email Notification by publishing an event when the user is registered.
diff --git a/guides/grails-events/v3/guide/services.adoc b/guides/grails-events/v3/guide/services.adoc
index 37319138c9b..bf86ccc74d4 100644
--- a/guides/grails-events/v3/guide/services.adoc
+++ b/guides/grails-events/v3/guide/services.adoc
@@ -19,4 +19,4 @@ In this guide, we save a `Notification` in the database.
include::../snippets/grails-app/services/demo/WelcomeEmailService.groovy[]
----
-<1> To consume an event use the https://async.grails.org/latest/api/grails/events/annotation/Subscriber.html[Subscriber] annotation. The method name `saveUser` is used by default for the event id, although it can start with the word "on". In other words either a method name of `saveUser` or `onSaveUser` would work for the this guide example.
+<1> To consume an event use the https://grails.apache.org/docs/latest/guide/async.html[Subscriber] annotation. The method name `saveUser` is used by default for the event id, although it can start with the word "on". In other words either a method name of `saveUser` or `onSaveUser` would work for the this guide example.
diff --git a/guides/grails-events/v3/guide/writingTheApp.adoc b/guides/grails-events/v3/guide/writingTheApp.adoc
index b30f8c7cbe6..2121bed35eb 100644
--- a/guides/grails-events/v3/guide/writingTheApp.adoc
+++ b/guides/grails-events/v3/guide/writingTheApp.adoc
@@ -12,4 +12,4 @@ Your project already contains the events dependency:
compile "org.grails.plugins:events"
----
-Grails Events capabilites documentation can be found in https://async.grails.org/latest/guide/index.html#events[async.grails.org].
\ No newline at end of file
+Grails Events capabilites documentation can be found in https://grails.apache.org/docs/latest/guide/async.html[async.grails.org].
\ No newline at end of file
diff --git a/guides/grails-events/v4/guide/gettingStarted.adoc b/guides/grails-events/v4/guide/gettingStarted.adoc
index 00b102bacab..db4b0b8849d 100644
--- a/guides/grails-events/v4/guide/gettingStarted.adoc
+++ b/guides/grails-events/v4/guide/gettingStarted.adoc
@@ -1,2 +1,2 @@
-In this guide, you are going to use https://async.grails.org/latest/guide/index.html#events[Grails Events] to handle a common scenario. A user registers in an application and the app sends the user a welcome email. For example, asking him to verify his email address.
+In this guide, you are going to use https://grails.apache.org/docs/latest/guide/async.html[Grails Events] to handle a common scenario. A user registers in an application and the app sends the user a welcome email. For example, asking him to verify his email address.
We are going to trigger the Email Notification by publishing an event when the user is registered.
diff --git a/guides/grails-events/v4/guide/services.adoc b/guides/grails-events/v4/guide/services.adoc
index 37319138c9b..bf86ccc74d4 100644
--- a/guides/grails-events/v4/guide/services.adoc
+++ b/guides/grails-events/v4/guide/services.adoc
@@ -19,4 +19,4 @@ In this guide, we save a `Notification` in the database.
include::../snippets/grails-app/services/demo/WelcomeEmailService.groovy[]
----
-<1> To consume an event use the https://async.grails.org/latest/api/grails/events/annotation/Subscriber.html[Subscriber] annotation. The method name `saveUser` is used by default for the event id, although it can start with the word "on". In other words either a method name of `saveUser` or `onSaveUser` would work for the this guide example.
+<1> To consume an event use the https://grails.apache.org/docs/latest/guide/async.html[Subscriber] annotation. The method name `saveUser` is used by default for the event id, although it can start with the word "on". In other words either a method name of `saveUser` or `onSaveUser` would work for the this guide example.
diff --git a/guides/grails-events/v4/guide/writingTheApp.adoc b/guides/grails-events/v4/guide/writingTheApp.adoc
index b30f8c7cbe6..2121bed35eb 100644
--- a/guides/grails-events/v4/guide/writingTheApp.adoc
+++ b/guides/grails-events/v4/guide/writingTheApp.adoc
@@ -12,4 +12,4 @@ Your project already contains the events dependency:
compile "org.grails.plugins:events"
----
-Grails Events capabilites documentation can be found in https://async.grails.org/latest/guide/index.html#events[async.grails.org].
\ No newline at end of file
+Grails Events capabilites documentation can be found in https://grails.apache.org/docs/latest/guide/async.html[async.grails.org].
\ No newline at end of file
diff --git a/guides/grails-file-download-excel/v3/guide/writingTheApp/controller.adoc b/guides/grails-file-download-excel/v3/guide/writingTheApp/controller.adoc
index 1d96a39fde7..e06309fc4f5 100644
--- a/guides/grails-file-download-excel/v3/guide/writingTheApp/controller.adoc
+++ b/guides/grails-file-download-excel/v3/guide/writingTheApp/controller.adoc
@@ -8,7 +8,7 @@ include::../../snippets/grails-app/controllers/example/grails/ExcelController.gr
<1> Implement `grails.core.support.GrailsConfigurationAware` to
configure mime types and encoding configuration.
-<2> A controller method can access the http://docs.grails.org/3.3.8/ref/Servlet%20API/response.html[response] object which is an instace of Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html[HttpServletResponse] class
+<2> A controller method can access the https://grails.apache.org/docs/3.3.8/ref/Servlet%20API/response.html[response] object which is an instace of Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html[HttpServletResponse] class
<3> Set `Content-Disposition` to indicate the file should be downloaded.
<4> Set the download `Content-Type`.
<5> Write excel file to output stream, flush and close it.
diff --git a/guides/grails-file-download-excel/v4/guide/writingTheApp/controller.adoc b/guides/grails-file-download-excel/v4/guide/writingTheApp/controller.adoc
index 1d96a39fde7..e06309fc4f5 100644
--- a/guides/grails-file-download-excel/v4/guide/writingTheApp/controller.adoc
+++ b/guides/grails-file-download-excel/v4/guide/writingTheApp/controller.adoc
@@ -8,7 +8,7 @@ include::../../snippets/grails-app/controllers/example/grails/ExcelController.gr
<1> Implement `grails.core.support.GrailsConfigurationAware` to
configure mime types and encoding configuration.
-<2> A controller method can access the http://docs.grails.org/3.3.8/ref/Servlet%20API/response.html[response] object which is an instace of Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html[HttpServletResponse] class
+<2> A controller method can access the https://grails.apache.org/docs/3.3.8/ref/Servlet%20API/response.html[response] object which is an instace of Servlet API’s https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html[HttpServletResponse] class
<3> Set `Content-Disposition` to indicate the file should be downloaded.
<4> Set the download `Content-Type`.
<5> Write excel file to output stream, flush and close it.
diff --git a/guides/grails-gorm-data-services/v3/guide/unitTest.adoc b/guides/grails-gorm-data-services/v3/guide/unitTest.adoc
index 0ddfb07cad9..ddf8fc77657 100644
--- a/guides/grails-gorm-data-services/v3/guide/unitTest.adoc
+++ b/guides/grails-gorm-data-services/v3/guide/unitTest.adoc
@@ -18,7 +18,7 @@ include::../snippets/src/test/groovy/example/grails/PersonDataServiceWithoutHibe
<5> In general you have to wrap your test execution logic in a session or transaction. You can obtain the PlatformTransactionManager from the HibernateDatastore.
<6> Typically you want to annotate your feature methods with the Rollback annotation which is used to rollback any changes made within each test.
-Luckily, http://plugins.grails.org/plugin/grails/hibernate5[Grails Hibernate Plugin] includes a utility class `grails.test.hibernate.HibernateSpec` which you could extend from and simplify
+Luckily, https://grails.apache.org/plugins.html[Grails Hibernate Plugin] includes a utility class `grails.test.hibernate.HibernateSpec` which you could extend from and simplify
the previous unit test:
[source, groovy]
diff --git a/guides/grails-gorm-data-services/v4/guide/unitTest.adoc b/guides/grails-gorm-data-services/v4/guide/unitTest.adoc
index 29072c660c1..7fd127d1062 100644
--- a/guides/grails-gorm-data-services/v4/guide/unitTest.adoc
+++ b/guides/grails-gorm-data-services/v4/guide/unitTest.adoc
@@ -21,7 +21,7 @@ include::../snippets/src/test/groovy/example/grails/PersonDataServiceWithoutHibe
<6> Typically you want to annotate your feature methods with the Rollback annotation which is used to rollback any changes made within each test.
<7> Cleanup the person created during the test.
-Luckily, http://plugins.grails.org/plugin/grails/hibernate5[Grails Hibernate Plugin] includes a utility class `grails.test.hibernate.HibernateSpec` which you could extend from and simplify
+Luckily, https://grails.apache.org/plugins.html[Grails Hibernate Plugin] includes a utility class `grails.test.hibernate.HibernateSpec` which you could extend from and simplify
the previous unit test:
[source, groovy]
diff --git a/guides/grails-javamelody/v4/guide/gettingStarted.adoc b/guides/grails-javamelody/v4/guide/gettingStarted.adoc
index e6fbcf7570d..50a95a905f3 100644
--- a/guides/grails-javamelody/v4/guide/gettingStarted.adoc
+++ b/guides/grails-javamelody/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
In this guide we will show you how to setup and use
https://github.com/javamelody/javamelody/wiki[JavaMelody] with a Grails 3 application.
We will be using the
-http://plugins.grails.org/plugin/sergiomichels/grails-melody-plugin[grails-melody-plugin]
+https://grails.apache.org/plugins.html[grails-melody-plugin]
diff --git a/guides/grails-logicaldelete/v3/guide/conclusion.adoc b/guides/grails-logicaldelete/v3/guide/conclusion.adoc
index 11adc2af2cd..cb86c36904e 100644
--- a/guides/grails-logicaldelete/v3/guide/conclusion.adoc
+++ b/guides/grails-logicaldelete/v3/guide/conclusion.adoc
@@ -1,4 +1,4 @@
NOTE: The goal of this guide is to show you the potential of the logical delete plugin, not a perfect implementation of undo functionality. For example, in this app we should protect the `undoDelete` action to be randomly invoked.
To learn more, read more http://grailsblog.objectcomputing.com/posts/2018/04/05/introducing-the-grails-3-gorm-logical-delete-plugin.html[Introducing the Grails 3 GORM Logical Delete plugin]'s blog post and
-read the http://plugins.grails.org/plugin/grails/gorm-logical-delete[plugin docs].
\ No newline at end of file
+read the https://grails.apache.org/plugins.html[plugin docs].
\ No newline at end of file
diff --git a/guides/grails-logicaldelete/v3/guide/gettingStarted.adoc b/guides/grails-logicaldelete/v3/guide/gettingStarted.adoc
index 5f5babcbff0..1df909c448f 100644
--- a/guides/grails-logicaldelete/v3/guide/gettingStarted.adoc
+++ b/guides/grails-logicaldelete/v3/guide/gettingStarted.adoc
@@ -1 +1 @@
-In this guide, we will introduce you http://plugins.grails.org/plugin/grails/gorm-logical-delete[GORM Logical Delete] plugin.
+In this guide, we will introduce you https://grails.apache.org/plugins.html[GORM Logical Delete] plugin.
diff --git a/guides/grails-logicaldelete/v3/guide/runningTheApp.adoc b/guides/grails-logicaldelete/v3/guide/runningTheApp.adoc
index 8433a346454..70e948deced 100644
--- a/guides/grails-logicaldelete/v3/guide/runningTheApp.adoc
+++ b/guides/grails-logicaldelete/v3/guide/runningTheApp.adoc
@@ -3,7 +3,7 @@ ____
Reference to a record that remains in the database, but is not included in comparisons or retrieved in searches.
____
-In this guide, we use the http://plugins.grails.org/plugin/grails/gorm-logical-delete[GORM Logical Delete] plugin to create
+In this guide, we use the https://grails.apache.org/plugins.html[GORM Logical Delete] plugin to create
Logical deletion into a Grails application.
We will create a delete button and undo functionality in a book collection.
diff --git a/guides/grails-logicaldelete/v4/guide/conclusion.adoc b/guides/grails-logicaldelete/v4/guide/conclusion.adoc
index 11adc2af2cd..cb86c36904e 100644
--- a/guides/grails-logicaldelete/v4/guide/conclusion.adoc
+++ b/guides/grails-logicaldelete/v4/guide/conclusion.adoc
@@ -1,4 +1,4 @@
NOTE: The goal of this guide is to show you the potential of the logical delete plugin, not a perfect implementation of undo functionality. For example, in this app we should protect the `undoDelete` action to be randomly invoked.
To learn more, read more http://grailsblog.objectcomputing.com/posts/2018/04/05/introducing-the-grails-3-gorm-logical-delete-plugin.html[Introducing the Grails 3 GORM Logical Delete plugin]'s blog post and
-read the http://plugins.grails.org/plugin/grails/gorm-logical-delete[plugin docs].
\ No newline at end of file
+read the https://grails.apache.org/plugins.html[plugin docs].
\ No newline at end of file
diff --git a/guides/grails-logicaldelete/v4/guide/gettingStarted.adoc b/guides/grails-logicaldelete/v4/guide/gettingStarted.adoc
index 5f5babcbff0..1df909c448f 100644
--- a/guides/grails-logicaldelete/v4/guide/gettingStarted.adoc
+++ b/guides/grails-logicaldelete/v4/guide/gettingStarted.adoc
@@ -1 +1 @@
-In this guide, we will introduce you http://plugins.grails.org/plugin/grails/gorm-logical-delete[GORM Logical Delete] plugin.
+In this guide, we will introduce you https://grails.apache.org/plugins.html[GORM Logical Delete] plugin.
diff --git a/guides/grails-logicaldelete/v4/guide/runningTheApp.adoc b/guides/grails-logicaldelete/v4/guide/runningTheApp.adoc
index 8433a346454..70e948deced 100644
--- a/guides/grails-logicaldelete/v4/guide/runningTheApp.adoc
+++ b/guides/grails-logicaldelete/v4/guide/runningTheApp.adoc
@@ -3,7 +3,7 @@ ____
Reference to a record that remains in the database, but is not included in comparisons or retrieved in searches.
____
-In this guide, we use the http://plugins.grails.org/plugin/grails/gorm-logical-delete[GORM Logical Delete] plugin to create
+In this guide, we use the https://grails.apache.org/plugins.html[GORM Logical Delete] plugin to create
Logical deletion into a Grails application.
We will create a delete button and undo functionality in a book collection.
diff --git a/guides/grails-micronaut-http/v5/guide/test.adoc b/guides/grails-micronaut-http/v5/guide/test.adoc
index e40eb9468f0..49d2582d864 100644
--- a/guides/grails-micronaut-http/v5/guide/test.adoc
+++ b/guides/grails-micronaut-http/v5/guide/test.adoc
@@ -1,5 +1,5 @@
The Micronaut Client can also be used for testing purposes with Spock. In our music app let's create a domain object to capture
-record labels. We will use the grails built-in https://docs.grails.org/latest/guide/REST.html#domainResources[REST API for domain classes].
+record labels. We will use the grails built-in https://grails.apache.org/docs/latest/guide/REST.html#domainResources[REST API for domain classes].
Create a domain object and tag it with `@Resource` and a given URI. This will expose REST functionality for the object.
diff --git a/guides/grails-micronaut-kafka/v4/guide/originalAppGrails.adoc b/guides/grails-micronaut-kafka/v4/guide/originalAppGrails.adoc
index 40eb4807cf5..e5e090bf412 100644
--- a/guides/grails-micronaut-kafka/v4/guide/originalAppGrails.adoc
+++ b/guides/grails-micronaut-kafka/v4/guide/originalAppGrails.adoc
@@ -73,7 +73,7 @@ Add the following mapping to `UrlMappings`:
include::../snippets/grails-app/controllers/example/grails/UrlMappings.groovy[tag=isbn]
----
-Create two http://views.grails.org/latest/#_json_views[JSON Views] for the controller's actions:
+Create two https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] for the controller's actions:
[source,groovy]
.grails-app/views/books/_book.gson
diff --git a/guides/grails-multi-datasource/v3/guide/views.adoc b/guides/grails-multi-datasource/v3/guide/views.adoc
index 634d6f417c6..48e8af0cefe 100644
--- a/guides/grails-multi-datasource/v3/guide/views.adoc
+++ b/guides/grails-multi-datasource/v3/guide/views.adoc
@@ -1,4 +1,4 @@
-Add multiple http://views.grails.org/latest/[JSON Views] to render the output.
+Add multiple https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] to render the output.
[source,groovy]
.grails-app/views/book/_book.gson
diff --git a/guides/grails-multi-datasource/v4/guide/views.adoc b/guides/grails-multi-datasource/v4/guide/views.adoc
index 634d6f417c6..48e8af0cefe 100644
--- a/guides/grails-multi-datasource/v4/guide/views.adoc
+++ b/guides/grails-multi-datasource/v4/guide/views.adoc
@@ -1,4 +1,4 @@
-Add multiple http://views.grails.org/latest/[JSON Views] to render the output.
+Add multiple https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] to render the output.
[source,groovy]
.grails-app/views/book/_book.gson
diff --git a/guides/grails-multi-project-build/v4/guide/featuresgradlefiles.adoc b/guides/grails-multi-project-build/v4/guide/featuresgradlefiles.adoc
index 048dc8b1e5d..50b9c1bcdc2 100644
--- a/guides/grails-multi-project-build/v4/guide/featuresgradlefiles.adoc
+++ b/guides/grails-multi-project-build/v4/guide/featuresgradlefiles.adoc
@@ -4,7 +4,7 @@ files for different features.
Imagine you have Geb tests in several projects of your multi-project build.
We can encapsulate a set of dependencies to run
-http://guides.grails.org/grails-geb-multiple-browsers/guide/index.html[Geb tests for multiple browsers].
+https://grails.apache.org/guides/grails-geb-multiple-browsers/guide/index.html[Geb tests for multiple browsers].
[source, groovy]
.gradle/geb.gradle
diff --git a/guides/grails-oauth-google/v4/guide/gettingStarted.adoc b/guides/grails-oauth-google/v4/guide/gettingStarted.adoc
index d7a9c4a50b1..87bd8b8bc5c 100644
--- a/guides/grails-oauth-google/v4/guide/gettingStarted.adoc
+++ b/guides/grails-oauth-google/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
In this guide we will show you how to add Google OAuth2 authentication to your app using the
https://alvarosanchez.github.io/grails-spring-security-rest/latest/docs/index.html[Spring Security Rest] plugin.
-We will be using the http://plugins.grails.org/plugin/grails/spring-security-rest[Spring Security Rest] plugin
+We will be using the https://grails.apache.org/plugins.html[Spring Security Rest] plugin
diff --git a/guides/grails-on-circleci-basics/v4/guide/wheretoGoFromHere.adoc b/guides/grails-on-circleci-basics/v4/guide/wheretoGoFromHere.adoc
index 6ec7c6e437a..aa5df8c9d29 100644
--- a/guides/grails-on-circleci-basics/v4/guide/wheretoGoFromHere.adoc
+++ b/guides/grails-on-circleci-basics/v4/guide/wheretoGoFromHere.adoc
@@ -1,3 +1,3 @@
Read https://circleci.com/docs/2.0/[Circle CI 2.0] documentation to see what it is possible.
-For example, https://circleci.com/docs/2.0/workflows/[Circle CI workflows] ease the creation of pipelines to test, and http://guides.grails.org/tags/deployment.html[deploy your Grails applications].
\ No newline at end of file
+For example, https://circleci.com/docs/2.0/workflows/[Circle CI workflows] ease the creation of pipelines to test, and https://grails.apache.org/guides/tags/deployment.html[deploy your Grails applications].
\ No newline at end of file
diff --git a/guides/grails-rabbitmq/v4/guide/bookApplicationRabbit.adoc b/guides/grails-rabbitmq/v4/guide/bookApplicationRabbit.adoc
index 51336cbe2dc..4a412fc8123 100644
--- a/guides/grails-rabbitmq/v4/guide/bookApplicationRabbit.adoc
+++ b/guides/grails-rabbitmq/v4/guide/bookApplicationRabbit.adoc
@@ -20,7 +20,7 @@ include::../snippets/grails-app/conf/application.yml[indent=0, tag=mqConfig]
<5> Creation of a `bookqueue`
When a book's details is viewed we publish a message to RabbitMQ. In order to do that we create
-an http://docs.grails.org/latest/guide/single.html#interceptors[interceptor].
+an https://grails.apache.org/docs/latest/guide/single.html#interceptors[interceptor].
Create a new interceptor in the `grails-app/controllers/demo` called `BookShowInterceptor.groovy`.
diff --git a/guides/grails-rabbitmq/v4/guide/gettingStarted.adoc b/guides/grails-rabbitmq/v4/guide/gettingStarted.adoc
index 040753fe4e2..8b1bf6d277f 100644
--- a/guides/grails-rabbitmq/v4/guide/gettingStarted.adoc
+++ b/guides/grails-rabbitmq/v4/guide/gettingStarted.adoc
@@ -1,2 +1,2 @@
In this guide we will show you how to setup and use https://www.rabbitmq.com/[RabbitMQ] with a Grails 3 application.
-We will be using the http://plugins.grails.org/plugin/budjb/rabbitmq-native[rabbitmq-native] plugin
+We will be using the https://grails.apache.org/plugins.html[rabbitmq-native] plugin
diff --git a/guides/grails-restapi-angularjs/v4/guide/domainClass.adoc b/guides/grails-restapi-angularjs/v4/guide/domainClass.adoc
index 3fdf73c56d6..9c055ceed34 100644
--- a/guides/grails-restapi-angularjs/v4/guide/domainClass.adoc
+++ b/guides/grails-restapi-angularjs/v4/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store Todos. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store Todos. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
@@ -15,7 +15,7 @@ The `Todo` domain class is our data model. We define different properties to sto
include::../snippets/grails-app/domain/demo/Todo.groovy[indent=0]
----
-With a http://docs.grails.org/latest/guide/testing.html[Unit Test], we test that `name` is a required property.
+With a https://grails.apache.org/docs/latest/guide/testing.html[Unit Test], we test that `name` is a required property.
[source,groovy]
./src/test/groovy/demo/TodoSpec.groovy
@@ -39,7 +39,7 @@ include::../snippets/grails-app/init/demo/BootStrap.groovy[indent=0]
include::../snippets/grails-app/domain/demo/Todo.groovy[indent=0,lines=3..6]
----
-This annotation exposes the `Todo` domain class as a https://docs.grails.org/latest/guide/webServices.html#domainResources[REST resource]
+This annotation exposes the `Todo` domain class as a https://grails.apache.org/docs/latest/guide/webServices.html#domainResources[REST resource]
____
The easiest way to create a RESTful API in Grails is to expose a domain class as a REST resource.
diff --git a/guides/grails-restapi-angularjs/v4/guide/enableCors.adoc b/guides/grails-restapi-angularjs/v4/guide/enableCors.adoc
index a977ee98cb4..162fb32962a 100644
--- a/guides/grails-restapi-angularjs/v4/guide/enableCors.adoc
+++ b/guides/grails-restapi-angularjs/v4/guide/enableCors.adoc
@@ -1,4 +1,4 @@
-Because the client side (AngularJS) and server side (Grails) will be running on separate ports, https://docs.grails.org/latest/guide/theWebLayer.html#cors[CORS] configuration is required.
+Because the client side (AngularJS) and server side (Grails) will be running on separate ports, https://grails.apache.org/docs/latest/guide/theWebLayer.html#cors[CORS] configuration is required.
Modify your `application.yml` to enable CORS
diff --git a/guides/grails-restapi-angularjs/v4/guide/writingTheApp.adoc b/guides/grails-restapi-angularjs/v4/guide/writingTheApp.adoc
index 28a3e8b8fb0..9ae72151099 100644
--- a/guides/grails-restapi-angularjs/v4/guide/writingTheApp.adoc
+++ b/guides/grails-restapi-angularjs/v4/guide/writingTheApp.adoc
@@ -1,4 +1,4 @@
-The initial project, which we are going to work on, was generated with http://docs.grails.org/latest/guide/webServices.html#restProfile[Grails REST profile].
+The initial project, which we are going to work on, was generated with https://grails.apache.org/docs/latest/guide/webServices.html#restProfile[Grails REST profile].
[source,bash]
----
diff --git a/guides/grails-soap/v3/guide/soapLibrary.adoc b/guides/grails-soap/v3/guide/soapLibrary.adoc
index e23deb3051e..4e29e7edaa3 100644
--- a/guides/grails-soap/v3/guide/soapLibrary.adoc
+++ b/guides/grails-soap/v3/guide/soapLibrary.adoc
@@ -16,7 +16,7 @@ We encapsulate the SOAP code in Grails service:
include::../snippets/grails-app/services/demo/VatService.groovy[]
----
-We test it using the http://testing.grails.org[Grails Testing Framework]
+We test it using the https://grails.apache.org/docs/latest/guide/testing.html[Grails Testing Framework]
[source,groovy]
.src/test/groovy/demo/VatServiceSpec.groovy
diff --git a/guides/grails-soap/v3/guide/test.adoc b/guides/grails-soap/v3/guide/test.adoc
index a871bef362e..0cf01b8cd5c 100644
--- a/guides/grails-soap/v3/guide/test.adoc
+++ b/guides/grails-soap/v3/guide/test.adoc
@@ -1,4 +1,4 @@
-Add several Geb dependencies. Read our guide http://guides.grails.org/grails-geb-multiple-browsers/guide/index.html[Run Grails Geb Functional Tests with Multiple Browsers] to learn more.
+Add several Geb dependencies. Read our guide https://grails.apache.org/guides/grails-geb-multiple-browsers/guide/index.html[Run Grails Geb Functional Tests with Multiple Browsers] to learn more.
[source,groovy]
.build.gradle
diff --git a/guides/grails-soap/v4/guide/soapLibrary.adoc b/guides/grails-soap/v4/guide/soapLibrary.adoc
index e23deb3051e..4e29e7edaa3 100644
--- a/guides/grails-soap/v4/guide/soapLibrary.adoc
+++ b/guides/grails-soap/v4/guide/soapLibrary.adoc
@@ -16,7 +16,7 @@ We encapsulate the SOAP code in Grails service:
include::../snippets/grails-app/services/demo/VatService.groovy[]
----
-We test it using the http://testing.grails.org[Grails Testing Framework]
+We test it using the https://grails.apache.org/docs/latest/guide/testing.html[Grails Testing Framework]
[source,groovy]
.src/test/groovy/demo/VatServiceSpec.groovy
diff --git a/guides/grails-soap/v4/guide/test.adoc b/guides/grails-soap/v4/guide/test.adoc
index be47aedcde5..48b2ad460ca 100644
--- a/guides/grails-soap/v4/guide/test.adoc
+++ b/guides/grails-soap/v4/guide/test.adoc
@@ -1,4 +1,4 @@
-Add several Geb dependencies. Read our guide http://guides.grails.org/grails-geb-multiple-browsers/guide/index.html[Run Grails Geb Functional Tests with Multiple Browsers] to learn more.
+Add several Geb dependencies. Read our guide https://grails.apache.org/guides/grails-geb-multiple-browsers/guide/index.html[Run Grails Geb Functional Tests with Multiple Browsers] to learn more.
[source,groovy]
.build.gradle
diff --git a/guides/grails-taglib-wyswyg-trix/v3/guide/domainClass.adoc b/guides/grails-taglib-wyswyg-trix/v3/guide/domainClass.adoc
index fcbd1e501ba..451fbaa72ef 100644
--- a/guides/grails-taglib-wyswyg-trix/v3/guide/domainClass.adoc
+++ b/guides/grails-taglib-wyswyg-trix/v3/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store _Announcement_ entities. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store _Announcement_ entities. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
diff --git a/guides/grails-taglib-wyswyg-trix/v3/guide/taglib.adoc b/guides/grails-taglib-wyswyg-trix/v3/guide/taglib.adoc
index dafac42e458..ce5133eac9d 100644
--- a/guides/grails-taglib-wyswyg-trix/v3/guide/taglib.adoc
+++ b/guides/grails-taglib-wyswyg-trix/v3/guide/taglib.adoc
@@ -13,7 +13,7 @@ The TagLib https://github.com/basecamp/trix#integrating-with-forms[integrates Tr
include::../snippets/grails-app/taglib/demo/TrixTagLib.groovy[indent=0]
----
-<1> We use a http://docs.grails.org/latest/guide/theWebLayer.html#namespaces[custom name space]; _trix_
+<1> We use a https://grails.apache.org/docs/latest/guide/theWebLayer.html#namespaces[custom name space]; _trix_
<2> By default we encode as _Text_ but the value, if present, is encoded as _Html_
And we test the _TagLib_:
diff --git a/guides/grails-taglib-wyswyg-trix/v4/guide/domainClass.adoc b/guides/grails-taglib-wyswyg-trix/v4/guide/domainClass.adoc
index fcbd1e501ba..451fbaa72ef 100644
--- a/guides/grails-taglib-wyswyg-trix/v4/guide/domainClass.adoc
+++ b/guides/grails-taglib-wyswyg-trix/v4/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store _Announcement_ entities. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store _Announcement_ entities. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
diff --git a/guides/grails-taglib-wyswyg-trix/v4/guide/taglib.adoc b/guides/grails-taglib-wyswyg-trix/v4/guide/taglib.adoc
index dafac42e458..ce5133eac9d 100644
--- a/guides/grails-taglib-wyswyg-trix/v4/guide/taglib.adoc
+++ b/guides/grails-taglib-wyswyg-trix/v4/guide/taglib.adoc
@@ -13,7 +13,7 @@ The TagLib https://github.com/basecamp/trix#integrating-with-forms[integrates Tr
include::../snippets/grails-app/taglib/demo/TrixTagLib.groovy[indent=0]
----
-<1> We use a http://docs.grails.org/latest/guide/theWebLayer.html#namespaces[custom name space]; _trix_
+<1> We use a https://grails.apache.org/docs/latest/guide/theWebLayer.html#namespaces[custom name space]; _trix_
<2> By default we encode as _Text_ but the value, if present, is encoded as _Html_
And we test the _TagLib_:
diff --git a/guides/grails-test-domain-class-constraints/v3/guide/domainClass.adoc b/guides/grails-test-domain-class-constraints/v3/guide/domainClass.adoc
index d89757e9062..d1261871dc5 100644
--- a/guides/grails-test-domain-class-constraints/v3/guide/domainClass.adoc
+++ b/guides/grails-test-domain-class-constraints/v3/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store _Hotel_ entities. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store _Hotel_ entities. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
@@ -19,7 +19,7 @@ The `Hotel` domain class is our data model. We define different properties to st
include::../snippets/grails-app/domain/demo/Hotel.groovy[indent=0]
----
-We define multiple https://docs.grails.org/latest/ref/Constraints/Usage.html[validation constraints]
+We define multiple https://grails.apache.org/docs/latest/ref/Constraints/Usage.html[validation constraints]
____
Constraints provide Grails with a declarative DSL for defining validation rules, schema generation and CRUD generation meta data.
@@ -27,25 +27,25 @@ ____
Grails comes with multiple constraints ready to use:
-* https://docs.grails.org/latest/ref/Constraints/attributes.html[attributes]
-* https://docs.grails.org/latest/ref/Constraints/bindable.html[bindable]
-* https://docs.grails.org/latest/ref/Constraints/blank.html[blank]
-* https://docs.grails.org/latest/ref/Constraints/creditCard.html[creditCard]
-* https://docs.grails.org/latest/ref/Constraints/email.html[email]
-* https://docs.grails.org/latest/ref/Constraints/inList.html[inList]
-* https://docs.grails.org/latest/ref/Constraints/matches.html[matches]
-* https://docs.grails.org/latest/ref/Constraints/max.html[max]
-* https://docs.grails.org/latest/ref/Constraints/maxSize.html[maxSize]
-* https://docs.grails.org/latest/ref/Constraints/min.html[min]
-* https://docs.grails.org/latest/ref/Constraints/minSize.html[minSize]
-* https://docs.grails.org/latest/ref/Constraints/notEqual.html[notEqual]
-* https://docs.grails.org/latest/ref/Constraints/nullable.html[nullable]
-* https://docs.grails.org/latest/ref/Constraints/range.html[range]
-* https://docs.grails.org/latest/ref/Constraints/scale.html[scale]
-* https://docs.grails.org/latest/ref/Constraints/size.html[size]
-* https://docs.grails.org/latest/ref/Constraints/unique.html[unique]
-* https://docs.grails.org/latest/ref/Constraints/url.html[url]
-* https://docs.grails.org/latest/ref/Constraints/validator.html[validator]
-* https://docs.grails.org/latest/ref/Constraints/widget.html[widget]
-
-NOTE: You can define your https://docs.grails.org/latest/ref/Constraints/validator.html[custom validators] if needed.
+* https://grails.apache.org/docs/latest/ref/Constraints/attributes.html[attributes]
+* https://grails.apache.org/docs/latest/ref/Constraints/bindable.html[bindable]
+* https://grails.apache.org/docs/latest/ref/Constraints/blank.html[blank]
+* https://grails.apache.org/docs/latest/ref/Constraints/creditCard.html[creditCard]
+* https://grails.apache.org/docs/latest/ref/Constraints/email.html[email]
+* https://grails.apache.org/docs/latest/ref/Constraints/inList.html[inList]
+* https://grails.apache.org/docs/latest/ref/Constraints/matches.html[matches]
+* https://grails.apache.org/docs/latest/ref/Constraints/max.html[max]
+* https://grails.apache.org/docs/latest/ref/Constraints/maxSize.html[maxSize]
+* https://grails.apache.org/docs/latest/ref/Constraints/min.html[min]
+* https://grails.apache.org/docs/latest/ref/Constraints/minSize.html[minSize]
+* https://grails.apache.org/docs/latest/ref/Constraints/notEqual.html[notEqual]
+* https://grails.apache.org/docs/latest/ref/Constraints/nullable.html[nullable]
+* https://grails.apache.org/docs/latest/ref/Constraints/range.html[range]
+* https://grails.apache.org/docs/latest/ref/Constraints/scale.html[scale]
+* https://grails.apache.org/docs/latest/ref/Constraints/size.html[size]
+* https://grails.apache.org/docs/latest/ref/Constraints/unique.html[unique]
+* https://grails.apache.org/docs/latest/ref/Constraints/url.html[url]
+* https://grails.apache.org/docs/latest/ref/Constraints/validator.html[validator]
+* https://grails.apache.org/docs/latest/ref/Constraints/widget.html[widget]
+
+NOTE: You can define your https://grails.apache.org/docs/latest/ref/Constraints/validator.html[custom validators] if needed.
diff --git a/guides/grails-test-domain-class-constraints/v3/guide/unitTests.adoc b/guides/grails-test-domain-class-constraints/v3/guide/unitTests.adoc
index b0709a96ae4..b0f4d585018 100644
--- a/guides/grails-test-domain-class-constraints/v3/guide/unitTests.adoc
+++ b/guides/grails-test-domain-class-constraints/v3/guide/unitTests.adoc
@@ -1,5 +1,5 @@
-We want to http://docs.grails.org/latest/guide/testing.html[unit test] our validation constraints.
+We want to https://grails.apache.org/docs/latest/guide/testing.html[unit test] our validation constraints.
Implement the `DomainUnitTest` trait. It indicates we are testing a Grails artifact; a domain class.
@@ -97,12 +97,12 @@ latitude nullable: true, range: -90..90
longitude nullable: true, range: -180..180
----
-However, a value such as `latitude` of 90.1 will be a valid value using the https://docs.grails.org/latest/ref/Constraints/range.html[Range Constraint]
+However, a value such as `latitude` of 90.1 will be a valid value using the https://grails.apache.org/docs/latest/ref/Constraints/range.html[Range Constraint]
____
Set to a Groovy range which can contain numbers in the form of an IntRange, dates or any object that implements Comparable and provides next and previous methods for navigation.
____
-Instead we are using a https://docs.grails.org/latest/ref/Constraints/validator.html[custom validation].
+Instead we are using a https://grails.apache.org/docs/latest/ref/Constraints/validator.html[custom validation].
[source,javascript]
./grails-app/domain/demo/Hotel.groovy
diff --git a/guides/grails-test-domain-class-constraints/v4/guide/domainClass.adoc b/guides/grails-test-domain-class-constraints/v4/guide/domainClass.adoc
index d89757e9062..d1261871dc5 100644
--- a/guides/grails-test-domain-class-constraints/v4/guide/domainClass.adoc
+++ b/guides/grails-test-domain-class-constraints/v4/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store _Hotel_ entities. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store _Hotel_ entities. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
@@ -19,7 +19,7 @@ The `Hotel` domain class is our data model. We define different properties to st
include::../snippets/grails-app/domain/demo/Hotel.groovy[indent=0]
----
-We define multiple https://docs.grails.org/latest/ref/Constraints/Usage.html[validation constraints]
+We define multiple https://grails.apache.org/docs/latest/ref/Constraints/Usage.html[validation constraints]
____
Constraints provide Grails with a declarative DSL for defining validation rules, schema generation and CRUD generation meta data.
@@ -27,25 +27,25 @@ ____
Grails comes with multiple constraints ready to use:
-* https://docs.grails.org/latest/ref/Constraints/attributes.html[attributes]
-* https://docs.grails.org/latest/ref/Constraints/bindable.html[bindable]
-* https://docs.grails.org/latest/ref/Constraints/blank.html[blank]
-* https://docs.grails.org/latest/ref/Constraints/creditCard.html[creditCard]
-* https://docs.grails.org/latest/ref/Constraints/email.html[email]
-* https://docs.grails.org/latest/ref/Constraints/inList.html[inList]
-* https://docs.grails.org/latest/ref/Constraints/matches.html[matches]
-* https://docs.grails.org/latest/ref/Constraints/max.html[max]
-* https://docs.grails.org/latest/ref/Constraints/maxSize.html[maxSize]
-* https://docs.grails.org/latest/ref/Constraints/min.html[min]
-* https://docs.grails.org/latest/ref/Constraints/minSize.html[minSize]
-* https://docs.grails.org/latest/ref/Constraints/notEqual.html[notEqual]
-* https://docs.grails.org/latest/ref/Constraints/nullable.html[nullable]
-* https://docs.grails.org/latest/ref/Constraints/range.html[range]
-* https://docs.grails.org/latest/ref/Constraints/scale.html[scale]
-* https://docs.grails.org/latest/ref/Constraints/size.html[size]
-* https://docs.grails.org/latest/ref/Constraints/unique.html[unique]
-* https://docs.grails.org/latest/ref/Constraints/url.html[url]
-* https://docs.grails.org/latest/ref/Constraints/validator.html[validator]
-* https://docs.grails.org/latest/ref/Constraints/widget.html[widget]
-
-NOTE: You can define your https://docs.grails.org/latest/ref/Constraints/validator.html[custom validators] if needed.
+* https://grails.apache.org/docs/latest/ref/Constraints/attributes.html[attributes]
+* https://grails.apache.org/docs/latest/ref/Constraints/bindable.html[bindable]
+* https://grails.apache.org/docs/latest/ref/Constraints/blank.html[blank]
+* https://grails.apache.org/docs/latest/ref/Constraints/creditCard.html[creditCard]
+* https://grails.apache.org/docs/latest/ref/Constraints/email.html[email]
+* https://grails.apache.org/docs/latest/ref/Constraints/inList.html[inList]
+* https://grails.apache.org/docs/latest/ref/Constraints/matches.html[matches]
+* https://grails.apache.org/docs/latest/ref/Constraints/max.html[max]
+* https://grails.apache.org/docs/latest/ref/Constraints/maxSize.html[maxSize]
+* https://grails.apache.org/docs/latest/ref/Constraints/min.html[min]
+* https://grails.apache.org/docs/latest/ref/Constraints/minSize.html[minSize]
+* https://grails.apache.org/docs/latest/ref/Constraints/notEqual.html[notEqual]
+* https://grails.apache.org/docs/latest/ref/Constraints/nullable.html[nullable]
+* https://grails.apache.org/docs/latest/ref/Constraints/range.html[range]
+* https://grails.apache.org/docs/latest/ref/Constraints/scale.html[scale]
+* https://grails.apache.org/docs/latest/ref/Constraints/size.html[size]
+* https://grails.apache.org/docs/latest/ref/Constraints/unique.html[unique]
+* https://grails.apache.org/docs/latest/ref/Constraints/url.html[url]
+* https://grails.apache.org/docs/latest/ref/Constraints/validator.html[validator]
+* https://grails.apache.org/docs/latest/ref/Constraints/widget.html[widget]
+
+NOTE: You can define your https://grails.apache.org/docs/latest/ref/Constraints/validator.html[custom validators] if needed.
diff --git a/guides/grails-test-domain-class-constraints/v4/guide/unitTests.adoc b/guides/grails-test-domain-class-constraints/v4/guide/unitTests.adoc
index b0709a96ae4..b0f4d585018 100644
--- a/guides/grails-test-domain-class-constraints/v4/guide/unitTests.adoc
+++ b/guides/grails-test-domain-class-constraints/v4/guide/unitTests.adoc
@@ -1,5 +1,5 @@
-We want to http://docs.grails.org/latest/guide/testing.html[unit test] our validation constraints.
+We want to https://grails.apache.org/docs/latest/guide/testing.html[unit test] our validation constraints.
Implement the `DomainUnitTest` trait. It indicates we are testing a Grails artifact; a domain class.
@@ -97,12 +97,12 @@ latitude nullable: true, range: -90..90
longitude nullable: true, range: -180..180
----
-However, a value such as `latitude` of 90.1 will be a valid value using the https://docs.grails.org/latest/ref/Constraints/range.html[Range Constraint]
+However, a value such as `latitude` of 90.1 will be a valid value using the https://grails.apache.org/docs/latest/ref/Constraints/range.html[Range Constraint]
____
Set to a Groovy range which can contain numbers in the form of an IntRange, dates or any object that implements Comparable and provides next and previous methods for navigation.
____
-Instead we are using a https://docs.grails.org/latest/ref/Constraints/validator.html[custom validation].
+Instead we are using a https://grails.apache.org/docs/latest/ref/Constraints/validator.html[custom validation].
[source,javascript]
./grails-app/domain/demo/Hotel.groovy
diff --git a/guides/grails-test-security/v3/guide/apiController.adoc b/guides/grails-test-security/v3/guide/apiController.adoc
index 8b862be78cf..ca4956da0fc 100644
--- a/guides/grails-test-security/v3/guide/apiController.adoc
+++ b/guides/grails-test-security/v3/guide/apiController.adoc
@@ -1,4 +1,4 @@
-To create the `Announcement` API controller we'll use the http://docs.grails.org/latest/ref/Command%20Line/create-controller.html[create-controller command]
+To create the `Announcement` API controller we'll use the https://grails.apache.org/docs/latest/ref/Command%20Line/create-controller.html[create-controller command]
[source, bash]
----
./grailsw create-controller ApiAnnouncement
@@ -14,7 +14,7 @@ We want this controller to handle any requests to _/api/announcements_. We'll ne
include::../snippets/grails-app/controllers/example/grails/UrlMappings.groovy[indent=0,lines="12"]
----
-The controller will be a http://docs.grails.org/latest/guide/webServices.html#extendingRestfulController[RestfulController], and will only respond with JSON.
+The controller will be a https://grails.apache.org/docs/latest/guide/webServices.html#extendingRestfulController[RestfulController], and will only respond with JSON.
[source,groovy]
.grails-app/controllers/example/grails/ApiAnnouncementController.groovy
diff --git a/guides/grails-test-security/v3/guide/domainClass.adoc b/guides/grails-test-security/v3/guide/domainClass.adoc
index e90906272fd..713f6088551 100644
--- a/guides/grails-test-security/v3/guide/domainClass.adoc
+++ b/guides/grails-test-security/v3/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-We'll create a http://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Domain Class], `Announcement`, which we are going to use as an example through this guide:
+We'll create a https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Domain Class], `Announcement`, which we are going to use as an example through this guide:
[source, bash]
----
diff --git a/guides/grails-test-security/v4/guide/apiController.adoc b/guides/grails-test-security/v4/guide/apiController.adoc
index 8b862be78cf..ca4956da0fc 100644
--- a/guides/grails-test-security/v4/guide/apiController.adoc
+++ b/guides/grails-test-security/v4/guide/apiController.adoc
@@ -1,4 +1,4 @@
-To create the `Announcement` API controller we'll use the http://docs.grails.org/latest/ref/Command%20Line/create-controller.html[create-controller command]
+To create the `Announcement` API controller we'll use the https://grails.apache.org/docs/latest/ref/Command%20Line/create-controller.html[create-controller command]
[source, bash]
----
./grailsw create-controller ApiAnnouncement
@@ -14,7 +14,7 @@ We want this controller to handle any requests to _/api/announcements_. We'll ne
include::../snippets/grails-app/controllers/example/grails/UrlMappings.groovy[indent=0,lines="12"]
----
-The controller will be a http://docs.grails.org/latest/guide/webServices.html#extendingRestfulController[RestfulController], and will only respond with JSON.
+The controller will be a https://grails.apache.org/docs/latest/guide/webServices.html#extendingRestfulController[RestfulController], and will only respond with JSON.
[source,groovy]
.grails-app/controllers/example/grails/ApiAnnouncementController.groovy
diff --git a/guides/grails-test-security/v4/guide/domainClass.adoc b/guides/grails-test-security/v4/guide/domainClass.adoc
index e90906272fd..713f6088551 100644
--- a/guides/grails-test-security/v4/guide/domainClass.adoc
+++ b/guides/grails-test-security/v4/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-We'll create a http://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Domain Class], `Announcement`, which we are going to use as an example through this guide:
+We'll create a https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Domain Class], `Announcement`, which we are going to use as an example through this guide:
[source, bash]
----
diff --git a/guides/grails-tvmlapp/v3/guide/controllerIndex.adoc b/guides/grails-tvmlapp/v3/guide/controllerIndex.adoc
index 278197b1c69..2e70d0e44cd 100644
--- a/guides/grails-tvmlapp/v3/guide/controllerIndex.adoc
+++ b/guides/grails-tvmlapp/v3/guide/controllerIndex.adoc
@@ -3,7 +3,7 @@ with the Grails Quickcasts:
image::stackTemplate.png[]
-Create a http://docs.grails.org/latest/guide/theWebLayer.html#controllers[Grails Controller] to handle requests
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#controllers[Grails Controller] to handle requests
include::{commondir}/common-quoteController.adoc[]
@@ -21,7 +21,7 @@ A request to _http://localhost:8080/quickcast_ executes the `index` action of `Q
include::../snippets/grails-app/controllers/com/ociweb/quickcasts/QuickcastController.groovy[indent=0,lines="1..4,8..11,17..18"]
----
-The `QuickcastController` index method renders every `Quickcast` using the next http://views.grails.org/latest/#_markup_views[Markup View]
+The `QuickcastController` index method renders every `Quickcast` using the next https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Markup View]
include::{commondir}/common-quoteMarkupViews.adoc[]
@@ -33,7 +33,7 @@ include::../snippets/grails-app/views/quickcast/index.gml[indent=0]
Markup Views are written in Groovy, end with the file extension `gml` and reside in the `grails-app/views` directory.
-Write a http://docs.grails.org/latest/guide/testing.html#functionalTesting[functional test] to test the XML generated is what we expect.
+Write a https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[functional test] to test the XML generated is what we expect.
[source,groovy]
./src/integration-test/groovy/com/ociweb/quickcasts/QuickcastControllerIndexSpec.groovy
diff --git a/guides/grails-tvmlapp/v3/guide/controllerShow.adoc b/guides/grails-tvmlapp/v3/guide/controllerShow.adoc
index cdc3e87385d..596c69242af 100644
--- a/guides/grails-tvmlapp/v3/guide/controllerShow.adoc
+++ b/guides/grails-tvmlapp/v3/guide/controllerShow.adoc
@@ -31,7 +31,7 @@ Fetching of related quickcasts is encapsulated in a Service.
include::../snippets/grails-app/services/com/ociweb/quickcasts/RelatedQuickcastsService.groovy[indent=0]
----
-The `QuickcastController` index method renders a `Quickcast` using the next http://views.grails.org/latest/#_markup_views[Markup View]
+The `QuickcastController` index method renders a `Quickcast` using the next https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Markup View]
[source,groovy]
./grails-app/views/quickcast/show.gml
diff --git a/guides/grails-tvmlapp/v3/guide/domainClass.adoc b/guides/grails-tvmlapp/v3/guide/domainClass.adoc
index 87b4b6c3909..ea5b1071810 100644
--- a/guides/grails-tvmlapp/v3/guide/domainClass.adoc
+++ b/guides/grails-tvmlapp/v3/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store Quickcasts. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store Quickcasts. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
@@ -15,7 +15,7 @@ The `Quickcast` domain class is our data model. We define different properties t
include::../snippets/grails-app/domain/com/ociweb/quickcasts/Quickcast.groovy[indent=0]
----
-With a http://docs.grails.org/latest/guide/testing.html[Unit Test], we test the property body is optional.
+With a https://grails.apache.org/docs/latest/guide/testing.html[Unit Test], we test the property body is optional.
[source,groovy]
./src/test/groovy/com/ociweb/quickcasts/QuickcastSpec.groovy
diff --git a/guides/grails-tvmlapp/v3/guide/internationalization.adoc b/guides/grails-tvmlapp/v3/guide/internationalization.adoc
index 23cd987c157..858ae84a2b5 100644
--- a/guides/grails-tvmlapp/v3/guide/internationalization.adoc
+++ b/guides/grails-tvmlapp/v3/guide/internationalization.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/i18n.html[Internationalization] is a first-class citizen in Grails.
+https://grails.apache.org/docs/latest/guide/i18n.html[Internationalization] is a first-class citizen in Grails.
include::{commondir}/common-quoteInternationalization.adoc[]
diff --git a/guides/grails-tvmlapp/v4/guide/controllerIndex.adoc b/guides/grails-tvmlapp/v4/guide/controllerIndex.adoc
index ccfcd8d8a3f..2a7e4ca1aed 100644
--- a/guides/grails-tvmlapp/v4/guide/controllerIndex.adoc
+++ b/guides/grails-tvmlapp/v4/guide/controllerIndex.adoc
@@ -3,7 +3,7 @@ with the Grails Quickcasts:
image::stackTemplate.png[]
-Create a http://docs.grails.org/latest/guide/theWebLayer.html#controllers[Grails Controller] to handle requests
+Create a https://grails.apache.org/docs/latest/guide/theWebLayer.html#controllers[Grails Controller] to handle requests
include::{commondir}/common-quoteController.adoc[]
@@ -21,7 +21,7 @@ A request to _http://localhost:8080/quickcast_ executes the `index` action of `Q
include::../snippets/grails-app/controllers/com/ociweb/quickcasts/QuickcastController.groovy[]
----
-The `QuickcastController` index method renders every `Quickcast` using the next http://views.grails.org/latest/#_markup_views[Markup View]
+The `QuickcastController` index method renders every `Quickcast` using the next https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Markup View]
include::{commondir}/common-quoteMarkupViews.adoc[]
@@ -33,7 +33,7 @@ include::../snippets/grails-app/views/quickcast/index.gml[indent=0]
Markup Views are written in Groovy, end with the file extension `gml` and reside in the `grails-app/views` directory.
-Write a http://docs.grails.org/latest/guide/testing.html#functionalTesting[functional test] to test the XML generated is what we expect.
+Write a https://grails.apache.org/docs/latest/guide/testing.html#functionalTesting[functional test] to test the XML generated is what we expect.
Add the Micronaut HTTP Client Dependency:
diff --git a/guides/grails-tvmlapp/v4/guide/controllerShow.adoc b/guides/grails-tvmlapp/v4/guide/controllerShow.adoc
index 71d6fc185e6..bf886e9b622 100644
--- a/guides/grails-tvmlapp/v4/guide/controllerShow.adoc
+++ b/guides/grails-tvmlapp/v4/guide/controllerShow.adoc
@@ -31,7 +31,7 @@ Fetching of related quickcasts is encapsulated in a Service.
include::../snippets/grails-app/services/com/ociweb/quickcasts/RelatedQuickcastsService.groovy[indent=0]
----
-The `QuickcastController` index method renders a `Quickcast` using the next http://views.grails.org/latest/#_markup_views[Markup View]
+The `QuickcastController` index method renders a `Quickcast` using the next https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Markup View]
[source,groovy]
./grails-app/views/quickcast/show.gml
diff --git a/guides/grails-tvmlapp/v4/guide/domainClass.adoc b/guides/grails-tvmlapp/v4/guide/domainClass.adoc
index 108d03e4b0e..a5f1eceed82 100644
--- a/guides/grails-tvmlapp/v4/guide/domainClass.adoc
+++ b/guides/grails-tvmlapp/v4/guide/domainClass.adoc
@@ -1,4 +1,4 @@
-Create a persistent entity to store Quickcasts. Most common way to handle persistence in Grails is the use of https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
+Create a persistent entity to store Quickcasts. Most common way to handle persistence in Grails is the use of https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[Grails Domain Classes]:
include::{commondir}/common-quoteDomainClass.adoc[]
@@ -15,7 +15,7 @@ The `Quickcast` domain class is our data model. We define different properties t
include::../snippets/grails-app/domain/com/ociweb/quickcasts/Quickcast.groovy[indent=0]
----
-With a http://docs.grails.org/latest/guide/testing.html[Unit Test], we test the property body is optional.
+With a https://grails.apache.org/docs/latest/guide/testing.html[Unit Test], we test the property body is optional.
[source,groovy]
./src/test/groovy/com/ociweb/quickcasts/QuickcastSpec.groovy
diff --git a/guides/grails-tvmlapp/v4/guide/internationalization.adoc b/guides/grails-tvmlapp/v4/guide/internationalization.adoc
index 23cd987c157..858ae84a2b5 100644
--- a/guides/grails-tvmlapp/v4/guide/internationalization.adoc
+++ b/guides/grails-tvmlapp/v4/guide/internationalization.adoc
@@ -1,4 +1,4 @@
-http://docs.grails.org/latest/guide/i18n.html[Internationalization] is a first-class citizen in Grails.
+https://grails.apache.org/docs/latest/guide/i18n.html[Internationalization] is a first-class citizen in Grails.
include::{commondir}/common-quoteInternationalization.adoc[]
diff --git a/guides/grails-upload-file/v3/guide/featuredImageCommand.adoc b/guides/grails-upload-file/v3/guide/featuredImageCommand.adoc
index c0fb3558dd1..ad11bd90f33 100644
--- a/guides/grails-upload-file/v3/guide/featuredImageCommand.adoc
+++ b/guides/grails-upload-file/v3/guide/featuredImageCommand.adoc
@@ -1,6 +1,6 @@
Each of our application entities ( hotels, restaurants and point of interest ) will have a featured image.
-To encapsulate the validation of the file being uploaded; we use a http://guides.grails.org/command-objects-and-forms/guide/index.html[Grails Command Object]
+To encapsulate the validation of the file being uploaded; we use a https://grails.apache.org/guides/command-objects-and-forms/guide/index.html[Grails Command Object]
[source, groovy]
./grails-app/controllers/example/grails/FeaturedImageCommand.groovy
diff --git a/guides/grails-upload-file/v3/guide/writingTheApp.adoc b/guides/grails-upload-file/v3/guide/writingTheApp.adoc
index 1615df2bfcb..e2f85d4ccc2 100644
--- a/guides/grails-upload-file/v3/guide/writingTheApp.adoc
+++ b/guides/grails-upload-file/v3/guide/writingTheApp.adoc
@@ -1,5 +1,5 @@
The `initial` folder contains a Grails 3 application created with the `web` profile.
-It has several Controllers, GORM Data Services, Domain classes and a simple CRUD interface built with http://gsp.grails.org[GSP]s.
+It has several Controllers, GORM Data Services, Domain classes and a simple CRUD interface built with https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[GSP]s.
It is an app to list tourism resources; hotels, restaurants, and points of interest.
In the next sections, you are going to add a feature to the app. Each of those resources may include a
diff --git a/guides/grails-upload-file/v4/guide/featuredImageCommand.adoc b/guides/grails-upload-file/v4/guide/featuredImageCommand.adoc
index c0fb3558dd1..ad11bd90f33 100644
--- a/guides/grails-upload-file/v4/guide/featuredImageCommand.adoc
+++ b/guides/grails-upload-file/v4/guide/featuredImageCommand.adoc
@@ -1,6 +1,6 @@
Each of our application entities ( hotels, restaurants and point of interest ) will have a featured image.
-To encapsulate the validation of the file being uploaded; we use a http://guides.grails.org/command-objects-and-forms/guide/index.html[Grails Command Object]
+To encapsulate the validation of the file being uploaded; we use a https://grails.apache.org/guides/command-objects-and-forms/guide/index.html[Grails Command Object]
[source, groovy]
./grails-app/controllers/example/grails/FeaturedImageCommand.groovy
diff --git a/guides/grails-upload-file/v4/guide/writingTheApp.adoc b/guides/grails-upload-file/v4/guide/writingTheApp.adoc
index 1615df2bfcb..e2f85d4ccc2 100644
--- a/guides/grails-upload-file/v4/guide/writingTheApp.adoc
+++ b/guides/grails-upload-file/v4/guide/writingTheApp.adoc
@@ -1,5 +1,5 @@
The `initial` folder contains a Grails 3 application created with the `web` profile.
-It has several Controllers, GORM Data Services, Domain classes and a simple CRUD interface built with http://gsp.grails.org[GSP]s.
+It has several Controllers, GORM Data Services, Domain classes and a simple CRUD interface built with https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[GSP]s.
It is an app to list tourism resources; hotels, restaurants, and points of interest.
In the next sections, you are going to add a feature to the app. Each of those resources may include a
diff --git a/guides/grails-vs-nodejs/v4/guide/authentication.adoc b/guides/grails-vs-nodejs/v4/guide/authentication.adoc
index cc302b092f8..582842ab6bb 100644
--- a/guides/grails-vs-nodejs/v4/guide/authentication.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/authentication.adoc
@@ -4,7 +4,7 @@ projects is https://projects.spring.io/spring-security/[Spring
Security]. It provides powerful authentication and access control for
Java web apps, and supports many authentication methods, from LDAP to
OAuth2. Even better, there is a set of
-http://plugins.grails.org/plugin/grails/spring-security-core[Grails
+https://grails.apache.org/plugins.html[Grails
plugins] that make Spring Security a breeze to set up.
Edit `server/build.gradle` again, and add the following two lines:
diff --git a/guides/grails-vs-nodejs/v4/guide/deployment.adoc b/guides/grails-vs-nodejs/v4/guide/deployment.adoc
index 1f6a1ccd219..a14da214e0e 100644
--- a/guides/grails-vs-nodejs/v4/guide/deployment.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/deployment.adoc
@@ -13,5 +13,5 @@ to be set accordingly).
An attractive way to package and deploy a Grails/React app is to bundle
both apps together into a single executable JAR file. This approach is
documented in tutorial form in the
-http://guides.grails.org/react-combined/guide/index.html[“Combining the
+https://grails.apache.org/guides/react-combined/guide/index.html[“Combining the
React profile projects”] Grails Guide.
\ No newline at end of file
diff --git a/guides/grails-vs-nodejs/v4/guide/flavorsByUser.adoc b/guides/grails-vs-nodejs/v4/guide/flavorsByUser.adoc
index e763849b62c..8c4a9193f50 100644
--- a/guides/grails-vs-nodejs/v4/guide/flavorsByUser.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/flavorsByUser.adoc
@@ -38,7 +38,7 @@ include::../snippets/server/grails-app/services/demo/UserIceCreamService.groovy[
}
----
-We render JSON with the help of http://views.grails.org[JSON Views]
+We render JSON with the help of https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views]
[source, groovy]
./server/grails-app/views/iceCream/index.gson
diff --git a/guides/grails-vs-nodejs/v4/guide/gorm.adoc b/guides/grails-vs-nodejs/v4/guide/gorm.adoc
index 238f2b8ca55..7f41dda3d36 100644
--- a/guides/grails-vs-nodejs/v4/guide/gorm.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/gorm.adoc
@@ -32,7 +32,7 @@ include::../snippets/server/grails-app/conf/application.yml[indent=0,tag=postgre
Now our Grails app is connected to our database, but we haven’t created
any tables yet. With Grails, there’s no need to create the database
schema manually (although you certainly can do so if you want). Instead,
-we’ll specify our domain model in code, by writing https://docs.grails.org/latest/ref/Domain%20Classes/Usage.html[*Domain Classes*].
+we’ll specify our domain model in code, by writing https://grails.apache.org/docs/latest/ref/Domain%20Classes/Usage.html[*Domain Classes*].
By convention, Grails will load any Groovy classes located under
`grails-app/domain` as Domain Classes. This means that GORM will map
@@ -68,7 +68,7 @@ create table user_ice_creams (
GORM is the data access toolkit used by Grails by default.
We can customize how the generated database schema looks like.
-http://docs.grails.org/latest/ref/Database%20Mapping/Usage.html[Database Mapping]
+https://grails.apache.org/docs/latest/ref/Database%20Mapping/Usage.html[Database Mapping]
____
Domain classes in Grails by default dictate the way they are mapped to the database using sensible defaults. You can customize these with the ORM Mapping DSL.
____
diff --git a/guides/grails-vs-nodejs/v4/guide/grails.adoc b/guides/grails-vs-nodejs/v4/guide/grails.adoc
index 1c9b3cd0b68..db843791580 100644
--- a/guides/grails-vs-nodejs/v4/guide/grails.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/grails.adoc
@@ -1,4 +1,4 @@
-From the http://grails.org[official website]:
+From the https://grails.apache.org[official website]:
[quote, Grails.org]
____
diff --git a/guides/grails-vs-nodejs/v4/guide/reactProfile.adoc b/guides/grails-vs-nodejs/v4/guide/reactProfile.adoc
index 0f231425afa..89d080d5593 100644
--- a/guides/grails-vs-nodejs/v4/guide/reactProfile.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/reactProfile.adoc
@@ -1,5 +1,5 @@
Every Grails project begins with a single `create-app` command. For the
-purposes of following along with this guide, you may choose to https://grails.org/download.html[install]
+purposes of following along with this guide, you may choose to https://grails.apache.org/download.html[install]
Grails via the official website, or using http://sdkman.io[sdkman] (recommended).
However, there is no need to install the framework on your machine to
create your Grails app - instead, let's browse to
@@ -50,7 +50,7 @@ separate “apps” for us - the backend Grails application, and the React
application (which in turn is generated via `create-react-app`). Gradle
treats these two apps as independent subprojects, with the above names.
This is called a
-http://guides.grails.org/grails-quickcasts-multi-project-builds/guide/index.html[multi-project
+https://grails.apache.org/guides/grails-quickcasts-multi-project-builds/guide/index.html[multi-project
build].
When running a Gradle “task” from the project root directory, anything
diff --git a/guides/grails-vs-nodejs/v4/guide/ssl.adoc b/guides/grails-vs-nodejs/v4/guide/ssl.adoc
index 412dd0cbaaf..7a01e5ed9cc 100644
--- a/guides/grails-vs-nodejs/v4/guide/ssl.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/ssl.adoc
@@ -22,7 +22,7 @@ When deploying to a server like Tomcat, it is necessary to use the Java KeyStore
++++
<ul>
<li><a href="https://symantec.tbs-certificates.co.uk/index.html.en">Convert PKCS12 to JKS</a></li>
-<li><a href="https://docs.grails.org/latest/guide/deployment.html#deploymentTasks">Configure JKS with Grails (docs)</a></li>
+<li><a href="https://grails.apache.org/docs/latest/guide/deployment.html#deploymentTasks">Configure JKS with Grails (docs)</a></li>
</ul>
++++
diff --git a/guides/grails-vs-nodejs/v4/guide/summary.adoc b/guides/grails-vs-nodejs/v4/guide/summary.adoc
index 34cb2fd491f..83024b7f85e 100644
--- a/guides/grails-vs-nodejs/v4/guide/summary.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/summary.adoc
@@ -7,8 +7,8 @@ Grails backend.
Grails offers a slew of powerful web development
features that we haven’t had occasion or time to demonstrate in this app
-- including http://views.grails.org/latest/[JSON views], http://guides.grails.org/using-hal-with-json-views[HAL+JSON support], http://gorm.grails.org/latest/hibernate/manual/index.html#constraints[custom data validation and
-constraints], http://guides.grails.org/neo4j-movies[NoSQL support], http://guides.grails.org/database-per-tenant[multi-tenancy], and much more. Please check
-out the http://guides.grails.org[Grails Guides website] for more
+- including https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON views], https://grails.apache.org/guides/using-hal-with-json-views[HAL+JSON support], http://gorm.grails.org/latest/hibernate/manual/index.html#constraints[custom data validation and
+constraints], https://grails.apache.org/guides/neo4j-movies[NoSQL support], https://grails.apache.org/guides/database-per-tenant[multi-tenancy], and much more. Please check
+out the https://grails.apache.org/guides[Grails Guides website] for more
tutorials on building fun and powerful apps with Grails (including
-several Guides http://guides.grails.org/building-a-react-app/[featuring React]).
\ No newline at end of file
+several Guides https://grails.apache.org/guides/building-a-react-app/[featuring React]).
\ No newline at end of file
diff --git a/guides/grails-vs-nodejs/v4/guide/websockets.adoc b/guides/grails-vs-nodejs/v4/guide/websockets.adoc
index 109f3ca14f8..a10c97dd52a 100644
--- a/guides/grails-vs-nodejs/v4/guide/websockets.adoc
+++ b/guides/grails-vs-nodejs/v4/guide/websockets.adoc
@@ -1,6 +1,6 @@
Our final server-side feature is to push “session timeout” events to the
client over a websocket connection. We’ll use another Grails plugin, the
-https://plugins.grails.org/plugin/zyro/grails-spring-websocket[Spring
+https://grails.apache.org/plugins.html[Spring
Websocket plugin], to support this feature.
Install the plugin by adding another line to our `build.gradle` file:
@@ -90,7 +90,7 @@ include::../snippets/server/grails-app/conf/application.yml[indent=0,tag=allowed
TIP: Grails applications can read config values set in a variety of
ways, including YAML files, Groovy files, and system properties. See the
-http://docs.grails.org/latest/guide/conf.html[Grails documentation] for
+https://grails.apache.org/docs/latest/guide/conf.html[Grails documentation] for
more on how to use configuration files.
That’s all for the Grails backend server - we have support for CORS (out
diff --git a/guides/grails_i18n/v3/guide/localeNavBar.adoc b/guides/grails_i18n/v3/guide/localeNavBar.adoc
index 03475d1d413..dda47f58320 100644
--- a/guides/grails_i18n/v3/guide/localeNavBar.adoc
+++ b/guides/grails_i18n/v3/guide/localeNavBar.adoc
@@ -6,7 +6,7 @@ We define the supported languages in a configuration property:
include::{sourcedir}/grails-app/conf/application.yml[tag=configurationLanguages]
----
-We are going to use a http://docs.grails.org/latest/guide/single.html#taglibs[Tag Library]
+We are going to use a https://grails.apache.org/docs/latest/guide/single.html#taglibs[Tag Library]
to render a languages dropdown:
image::languages_drop_down.png[]
@@ -40,5 +40,5 @@ include::{sourcedir}/grails-app/views/index.gsp[tag=navBarLocaleDropDown, indent
We supply to the Tag Lib the `request.forwardURI`
____
-http://docs.grails.org/latest/ref/Servlet%20API/request.html[forwardURI] - Useful for obtaining the current request URI since the request object’s requestURI property returns the original URI, not the matched one.
+https://grails.apache.org/docs/latest/ref/Servlet%20API/request.html[forwardURI] - Useful for obtaining the current request URI since the request object’s requestURI property returns the original URI, not the matched one.
____
diff --git a/guides/grails_i18n/v3/guide/writingTheApp.adoc b/guides/grails_i18n/v3/guide/writingTheApp.adoc
index 4175158c9a3..0a3d65ebcdb 100644
--- a/guides/grails_i18n/v3/guide/writingTheApp.adoc
+++ b/guides/grails_i18n/v3/guide/writingTheApp.adoc
@@ -1,3 +1,3 @@
-http://docs.grails.org/latest/guide/single.html#i18n[Grails supports Internationalization (i18n) out of the box] by leveraging the
+https://grails.apache.org/docs/latest/guide/single.html#i18n[Grails supports Internationalization (i18n) out of the box] by leveraging the
underlying Spring MVC internationalization support. With Grails you are able
to customize the text that appears in a view based on the user’s Locale
diff --git a/guides/grails_i18n/v4/guide/localeNavBar.adoc b/guides/grails_i18n/v4/guide/localeNavBar.adoc
index 03475d1d413..dda47f58320 100644
--- a/guides/grails_i18n/v4/guide/localeNavBar.adoc
+++ b/guides/grails_i18n/v4/guide/localeNavBar.adoc
@@ -6,7 +6,7 @@ We define the supported languages in a configuration property:
include::{sourcedir}/grails-app/conf/application.yml[tag=configurationLanguages]
----
-We are going to use a http://docs.grails.org/latest/guide/single.html#taglibs[Tag Library]
+We are going to use a https://grails.apache.org/docs/latest/guide/single.html#taglibs[Tag Library]
to render a languages dropdown:
image::languages_drop_down.png[]
@@ -40,5 +40,5 @@ include::{sourcedir}/grails-app/views/index.gsp[tag=navBarLocaleDropDown, indent
We supply to the Tag Lib the `request.forwardURI`
____
-http://docs.grails.org/latest/ref/Servlet%20API/request.html[forwardURI] - Useful for obtaining the current request URI since the request object’s requestURI property returns the original URI, not the matched one.
+https://grails.apache.org/docs/latest/ref/Servlet%20API/request.html[forwardURI] - Useful for obtaining the current request URI since the request object’s requestURI property returns the original URI, not the matched one.
____
diff --git a/guides/grails_i18n/v4/guide/writingTheApp.adoc b/guides/grails_i18n/v4/guide/writingTheApp.adoc
index 4175158c9a3..0a3d65ebcdb 100644
--- a/guides/grails_i18n/v4/guide/writingTheApp.adoc
+++ b/guides/grails_i18n/v4/guide/writingTheApp.adoc
@@ -1,3 +1,3 @@
-http://docs.grails.org/latest/guide/single.html#i18n[Grails supports Internationalization (i18n) out of the box] by leveraging the
+https://grails.apache.org/docs/latest/guide/single.html#i18n[Grails supports Internationalization (i18n) out of the box] by leveraging the
underlying Spring MVC internationalization support. With Grails you are able
to customize the text that appears in a view based on the user’s Locale
diff --git a/guides/grails_url_mappings/v4/guide/conclusion.adoc b/guides/grails_url_mappings/v4/guide/conclusion.adoc
index 79f8849495a..61e068f9ae0 100644
--- a/guides/grails_url_mappings/v4/guide/conclusion.adoc
+++ b/guides/grails_url_mappings/v4/guide/conclusion.adoc
@@ -1 +1 @@
-At this point you should be comfortable with the concept of URL mappings, and you have a good handle on the most important features. You can learn much more about the capabilities of URL mappings from the http://docs.grails.org/3.3.2/guide/single.html#urlmappings[Grails Documentation], including *namespaces*, RESTful *resource* mappings, *constraints*, and *wildcards*.
\ No newline at end of file
+At this point you should be comfortable with the concept of URL mappings, and you have a good handle on the most important features. You can learn much more about the capabilities of URL mappings from the https://grails.apache.org/docs/3.3.2/guide/single.html#urlmappings[Grails Documentation], including *namespaces*, RESTful *resource* mappings, *constraints*, and *wildcards*.
\ No newline at end of file
diff --git a/guides/grails_url_mappings/v4/guide/gettingStarted.adoc b/guides/grails_url_mappings/v4/guide/gettingStarted.adoc
index 3597ee43ea2..184df2f0d7c 100644
--- a/guides/grails_url_mappings/v4/guide/gettingStarted.adoc
+++ b/guides/grails_url_mappings/v4/guide/gettingStarted.adoc
@@ -1,3 +1,3 @@
-Whether you're building a traditional page-based application, a Single-Page App, or a microservice, having a logical, extendable API is a very important part of application design. Grails offers powerful support for building APIs with http://docs.grails.org/latest/guide/theWebLayer.html#urlmappings[*URL Mappings*].
+Whether you're building a traditional page-based application, a Single-Page App, or a microservice, having a logical, extendable API is a very important part of application design. Grails offers powerful support for building APIs with https://grails.apache.org/docs/latest/guide/theWebLayer.html#urlmappings[*URL Mappings*].
The sample application we are going to build will be a conference scheduling app, called `agenda`. We will have a simple domain model consisting of *Speakers*, *Talks*, an *Agenda* (which ties together speakers and talks), and a *Conference* (which has an agenda). We won't be creating the domain model in this guide, but we'll create the web layer that will sit above it for now.
\ No newline at end of file
diff --git a/guides/grails_url_mappings/v4/guide/testing.adoc b/guides/grails_url_mappings/v4/guide/testing.adoc
index f9fe5bc9fac..e7d83bb1b44 100644
--- a/guides/grails_url_mappings/v4/guide/testing.adoc
+++ b/guides/grails_url_mappings/v4/guide/testing.adoc
@@ -1,4 +1,4 @@
-The http://testing.grails.org[Grails Testing Support] library is the recommended way to write tests for most Grails artefacts, including URL mappings. The library is included in the current version of Grails, and it provides a `UrlMappingsUnitTest` trait that makes it easy to test URL mappings.
+The https://grails.apache.org/docs/latest/guide/testing.html[Grails Testing Support] library is the recommended way to write tests for most Grails artefacts, including URL mappings. The library is included in the current version of Grails, and it provides a `UrlMappingsUnitTest` trait that makes it easy to test URL mappings.
TIP: *Traits* are a powerful feature of the Groovy programming language, and many Grails features utilize them. You can create your own traits as well as part of your application code. See the http://docs.groovy-lang.org/next/html/documentation/core-traits.html[Groovy documentation] for more information.
diff --git a/guides/grails_url_mappings/v4/guide/urlMappings.adoc b/guides/grails_url_mappings/v4/guide/urlMappings.adoc
index 772ab3e1b9a..048851558cb 100644
--- a/guides/grails_url_mappings/v4/guide/urlMappings.adoc
+++ b/guides/grails_url_mappings/v4/guide/urlMappings.adoc
@@ -22,7 +22,7 @@ class UrlMappings {
The very first mapping in the `mappings` block is pretty straightforward. It has two components: a string, defining the URL pattern, and a closure, where options (such as *constraints*) can be specified to change the behavior of the mapping.
-TIP: See how to use URL constraints http://docs.grails.org/latest/guide/theWebLayer.html#applyingConstraints[here in the Grails documentation].
+TIP: See how to use URL constraints https://grails.apache.org/docs/latest/guide/theWebLayer.html#applyingConstraints[here in the Grails documentation].
The URL pattern can include variables, which are denoted by Groovy Strings within the pattern (e.g., `$controller` or `${controller}`. Grails has a few special wildcards which it supports out of the box. For example, `$controller` will be mapped to the name of a given controller, `$action` will be mapped to an action within that controller, and so forth. Optional variables are suffixed with a `?`. E.g., `/controller/$action?`
diff --git a/guides/neo4j-movies/v4/guide/byTitleEndpoint.adoc b/guides/neo4j-movies/v4/guide/byTitleEndpoint.adoc
index d3ab8b49def..48c1dce8c1e 100644
--- a/guides/neo4j-movies/v4/guide/byTitleEndpoint.adoc
+++ b/guides/neo4j-movies/v4/guide/byTitleEndpoint.adoc
@@ -62,7 +62,7 @@ TIP: If you wish to debug the Cypher query GORM executed then enable debug loggi
Although valid JSON, unfortunately this is not the exact format required to implement the Neo4j example application.
-To customize the JSON create a `grails-app/views/movie/_movie.gson` http://views.grails.org/latest/[JSON View] and populate it with the following contents:
+To customize the JSON create a `grails-app/views/movie/_movie.gson` https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON View] and populate it with the following contents:
[source,groovy]
.grails-app/views/movie/_movie.gson
diff --git a/guides/querying-gorm-dynamic-finders/v3/guide/specialForms/chainingDCAndNQ.adoc b/guides/querying-gorm-dynamic-finders/v3/guide/specialForms/chainingDCAndNQ.adoc
index a30f52c3263..53bcd48ef0c 100644
--- a/guides/querying-gorm-dynamic-finders/v3/guide/specialForms/chainingDCAndNQ.adoc
+++ b/guides/querying-gorm-dynamic-finders/v3/guide/specialForms/chainingDCAndNQ.adoc
@@ -6,7 +6,7 @@ by _chaining_ (i.e. appending) dynamic finders to them.
For example, let us find all the games that
use involve the "Hand Management" mechanic and have an average duration of less than 120
minutes. Finding all games using a specific mechanic can be done with the `Game` domain class
-http://docs.grails.org/latest/ref/Domain%20Classes/namedQueries.html[Named Query], `gamesWithMechanic`.
+https://grails.apache.org/docs/latest/ref/Domain%20Classes/namedQueries.html[Named Query], `gamesWithMechanic`.
[source,groovy]
----
include::complete/grails-app/domain/demo/Game.groovy[tag=gameNamedQueries]
diff --git a/guides/querying-gorm-dynamic-finders/v3/guide/updatingTheService/queryParameters.adoc b/guides/querying-gorm-dynamic-finders/v3/guide/updatingTheService/queryParameters.adoc
index 8a7bdd99d0a..9272463d0d2 100644
--- a/guides/querying-gorm-dynamic-finders/v3/guide/updatingTheService/queryParameters.adoc
+++ b/guides/querying-gorm-dynamic-finders/v3/guide/updatingTheService/queryParameters.adoc
@@ -58,5 +58,5 @@ result of a query. For robust code, you should consider adding a `sort` paramete
NOTE: There are a few more parameters available than are listed here. Please
refer to the documentation for
-http://docs.grails.org/latest/ref/Domain%20Classes/list.html[`list`] to see if they
+https://grails.apache.org/docs/latest/ref/Domain%20Classes/list.html[`list`] to see if they
apply to your situation.
diff --git a/guides/querying-gorm-dynamic-finders/v4/guide/specialForms/chainingDCAndNQ.adoc b/guides/querying-gorm-dynamic-finders/v4/guide/specialForms/chainingDCAndNQ.adoc
index a30f52c3263..53bcd48ef0c 100644
--- a/guides/querying-gorm-dynamic-finders/v4/guide/specialForms/chainingDCAndNQ.adoc
+++ b/guides/querying-gorm-dynamic-finders/v4/guide/specialForms/chainingDCAndNQ.adoc
@@ -6,7 +6,7 @@ by _chaining_ (i.e. appending) dynamic finders to them.
For example, let us find all the games that
use involve the "Hand Management" mechanic and have an average duration of less than 120
minutes. Finding all games using a specific mechanic can be done with the `Game` domain class
-http://docs.grails.org/latest/ref/Domain%20Classes/namedQueries.html[Named Query], `gamesWithMechanic`.
+https://grails.apache.org/docs/latest/ref/Domain%20Classes/namedQueries.html[Named Query], `gamesWithMechanic`.
[source,groovy]
----
include::complete/grails-app/domain/demo/Game.groovy[tag=gameNamedQueries]
diff --git a/guides/querying-gorm-dynamic-finders/v4/guide/updatingTheService/queryParameters.adoc b/guides/querying-gorm-dynamic-finders/v4/guide/updatingTheService/queryParameters.adoc
index 8a7bdd99d0a..9272463d0d2 100644
--- a/guides/querying-gorm-dynamic-finders/v4/guide/updatingTheService/queryParameters.adoc
+++ b/guides/querying-gorm-dynamic-finders/v4/guide/updatingTheService/queryParameters.adoc
@@ -58,5 +58,5 @@ result of a query. For robust code, you should consider adding a `sort` paramete
NOTE: There are a few more parameters available than are listed here. Please
refer to the documentation for
-http://docs.grails.org/latest/ref/Domain%20Classes/list.html[`list`] to see if they
+https://grails.apache.org/docs/latest/ref/Domain%20Classes/list.html[`list`] to see if they
apply to your situation.
diff --git a/guides/react-spring-security/v4/guide/server.adoc b/guides/react-spring-security/v4/guide/server.adoc
index c661636b472..6f79531091d 100644
--- a/guides/react-spring-security/v4/guide/server.adoc
+++ b/guides/react-spring-security/v4/guide/server.adoc
@@ -1,4 +1,4 @@
-NOTE: The `initial` project is based on the completed project from the http://guides.grails.org/building-a-react-app/guide/index.html[Building a React App] Guide. Please refer to that guide for details on the provided code.
+NOTE: The `initial` project is based on the completed project from the https://grails.apache.org/guides/building-a-react-app/guide/index.html[Building a React App] Guide. Please refer to that guide for details on the provided code.
Our first step in adding security to this project is to install the Spring Security plugin/s in our Grails app, and secure our API endpoints. The Spring Security REST plugin supports a stateless, token-based authentication model that is ideal for securing APIs and Single Page Applications. See the diagram below for an overview of the security model.
diff --git a/guides/resources/style/menu.html b/guides/resources/style/menu.html
index 85ed873c6e2..d8838deda5c 100644
--- a/guides/resources/style/menu.html
+++ b/guides/resources/style/menu.html
@@ -33,7 +33,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/ [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.k [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/guides/resources/style/referenceItem.html b/guides/resources/style/referenceItem.html
index 920c9ea7c7d..10f0ca77960 100644
--- a/guides/resources/style/referenceItem.html
+++ b/guides/resources/style/referenceItem.html
@@ -48,7 +48,7 @@
data-user-analytics-fingerprint-enabled="true"
data-modal-title="Apache Grails AI Assistant"
data-modal-example-questions-title="Try asking me..."
- data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://docs.grails.org/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa.ai/inte [...]
+ data-modal-disclaimer="This is a custom LLM for Apache Grails using [documentation](https://grails.apache.org/docs/latest/), [groovy documentation](https://docs.groovy-lang.org/docs/groovy-4.0.28/html/documentation/) [github issues](https://github.com/apache/grails-core/issues) and more.\n\nCompanies deploy assistants like this [](https://kapa.ai) on docs via [website widget](https://docs.kapa.ai/integrations/website-widget) (Docker, Reddit), in [support forms](https://docs.kapa. [...]
data-modal-example-questions="How does database migration work?,How does Spring Security work?"
data-button-text-color="#FBB576"
data-modal-header-bg-color="#FFFFFF"
diff --git a/guides/rest-hibernate/v3/guide/controller.adoc b/guides/rest-hibernate/v3/guide/controller.adoc
index 337c643e4ab..99b87c9f502 100644
--- a/guides/rest-hibernate/v3/guide/controller.adoc
+++ b/guides/rest-hibernate/v3/guide/controller.adoc
@@ -1,4 +1,4 @@
-With the data model defined now it time to write http://docs.grails.org/latest/guide/theWebLayer.html#controllers[a controller].
+With the data model defined now it time to write https://grails.apache.org/docs/latest/guide/theWebLayer.html#controllers[a controller].
The quickest way to do that is with the `create-restful-controller` command from a terminal window:
diff --git a/guides/rest-hibernate/v3/guide/gettingStarted.adoc b/guides/rest-hibernate/v3/guide/gettingStarted.adoc
index 8db22b0b3a7..b6c4da66628 100644
--- a/guides/rest-hibernate/v3/guide/gettingStarted.adoc
+++ b/guides/rest-hibernate/v3/guide/gettingStarted.adoc
@@ -1 +1 @@
-In this guide you are going to build a http://grails.org[Grails application] that uses http://gorm.grails.org/latest/hibernate[GORM for Hibernate] to access a SQL database and produce a JSON response in a RESTful manner.
+In this guide you are going to build a https://grails.apache.org[Grails application] that uses http://gorm.grails.org/latest/hibernate[GORM for Hibernate] to access a SQL database and produce a JSON response in a RESTful manner.
diff --git a/guides/rest-hibernate/v3/guide/json.adoc b/guides/rest-hibernate/v3/guide/json.adoc
index 28b3e1815b8..17ed3bba06b 100644
--- a/guides/rest-hibernate/v3/guide/json.adoc
+++ b/guides/rest-hibernate/v3/guide/json.adoc
@@ -1,4 +1,4 @@
-Grails uses http://views.grails.org[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
+Grails uses https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
The default view rendered if no specific view is found is `grails-app/views/object/_object.gson`:
@@ -59,4 +59,4 @@ In this trivialized example, we output the currency symbol based on the user's l
[{id:1,"name":"Apple","price":"$2.0"}]
----
-TIP: JSON Views are very flexible, for more information on customizing the output to your needs see http://views.grails.org[the documentation].
+TIP: JSON Views are very flexible, for more information on customizing the output to your needs see https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[the documentation].
diff --git a/guides/rest-hibernate/v4/guide/controller.adoc b/guides/rest-hibernate/v4/guide/controller.adoc
index 337c643e4ab..99b87c9f502 100644
--- a/guides/rest-hibernate/v4/guide/controller.adoc
+++ b/guides/rest-hibernate/v4/guide/controller.adoc
@@ -1,4 +1,4 @@
-With the data model defined now it time to write http://docs.grails.org/latest/guide/theWebLayer.html#controllers[a controller].
+With the data model defined now it time to write https://grails.apache.org/docs/latest/guide/theWebLayer.html#controllers[a controller].
The quickest way to do that is with the `create-restful-controller` command from a terminal window:
diff --git a/guides/rest-hibernate/v4/guide/gettingStarted.adoc b/guides/rest-hibernate/v4/guide/gettingStarted.adoc
index 8db22b0b3a7..b6c4da66628 100644
--- a/guides/rest-hibernate/v4/guide/gettingStarted.adoc
+++ b/guides/rest-hibernate/v4/guide/gettingStarted.adoc
@@ -1 +1 @@
-In this guide you are going to build a http://grails.org[Grails application] that uses http://gorm.grails.org/latest/hibernate[GORM for Hibernate] to access a SQL database and produce a JSON response in a RESTful manner.
+In this guide you are going to build a https://grails.apache.org[Grails application] that uses http://gorm.grails.org/latest/hibernate[GORM for Hibernate] to access a SQL database and produce a JSON response in a RESTful manner.
diff --git a/guides/rest-hibernate/v4/guide/json.adoc b/guides/rest-hibernate/v4/guide/json.adoc
index 28b3e1815b8..17ed3bba06b 100644
--- a/guides/rest-hibernate/v4/guide/json.adoc
+++ b/guides/rest-hibernate/v4/guide/json.adoc
@@ -1,4 +1,4 @@
-Grails uses http://views.grails.org[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
+Grails uses https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
The default view rendered if no specific view is found is `grails-app/views/object/_object.gson`:
@@ -59,4 +59,4 @@ In this trivialized example, we output the currency symbol based on the user's l
[{id:1,"name":"Apple","price":"$2.0"}]
----
-TIP: JSON Views are very flexible, for more information on customizing the output to your needs see http://views.grails.org[the documentation].
+TIP: JSON Views are very flexible, for more information on customizing the output to your needs see https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[the documentation].
diff --git a/guides/rest-mongodb/v4/guide/applyConstraints.adoc b/guides/rest-mongodb/v4/guide/applyConstraints.adoc
index 3910b7e8c1f..856e8d4bbe2 100644
--- a/guides/rest-mongodb/v4/guide/applyConstraints.adoc
+++ b/guides/rest-mongodb/v4/guide/applyConstraints.adoc
@@ -32,7 +32,7 @@ include::../snippets/src/test/groovy/demo/ProductSpec.groovy[tag=clazz]
<1> Spock allows you to define much more readable
<2> Override the `createMongoClient` method of the `MongoSpec` base class. Use something such as https://github.com/fakemongo/fongo[Fongo]; an in-memory java implementation of MongoDB.
<3> MongoSpec is an abstract class that will initialise GORM in the setup phase of the specification being executed
-<4> Use the https://testing.grails.org/latest/guide/index.html#unitTestingDomainClasses[grails.testing.gorm.DomainUnitTest] trait to unit test single domain class.
+<4> Use the https://grails.apache.org/docs/latest/guide/testing.html[grails.testing.gorm.DomainUnitTest] trait to unit test single domain class.
Add the fongo dependency to `build.gradle`
@@ -49,7 +49,7 @@ Now to run the test you can run `./gradlew check` from a terminal window or run
$ ./gradlew check
----
-Checkout http://guides.grails.org/grails-test-domain-class-constraints/guide/index.html[How to test domain class constraints?] guide to learn more about testing constraints.
+Checkout https://grails.apache.org/guides/grails-test-domain-class-constraints/guide/index.html[How to test domain class constraints?] guide to learn more about testing constraints.
diff --git a/guides/rest-mongodb/v4/guide/controller.adoc b/guides/rest-mongodb/v4/guide/controller.adoc
index de70e83ed55..30ea906e035 100644
--- a/guides/rest-mongodb/v4/guide/controller.adoc
+++ b/guides/rest-mongodb/v4/guide/controller.adoc
@@ -1,4 +1,4 @@
-With the data model defined now it time to write http://docs.grails.org/latest/guide/theWebLayer.html#controllers[a controller].
+With the data model defined now it time to write https://grails.apache.org/docs/latest/guide/theWebLayer.html#controllers[a controller].
The quickest way to do that is with the `create-restful-controller` command from a terminal window:
diff --git a/guides/rest-mongodb/v4/guide/gettingStarted.adoc b/guides/rest-mongodb/v4/guide/gettingStarted.adoc
index 5822dd14f0f..2993e8c6137 100644
--- a/guides/rest-mongodb/v4/guide/gettingStarted.adoc
+++ b/guides/rest-mongodb/v4/guide/gettingStarted.adoc
@@ -1 +1 @@
-In this guide you are going to build a http://grails.org[Grails application] that uses http://gorm.grails.org/latest/mongodb[GORM for MongoDB] to access http://mongodb.org[MongoDB] and produce a JSON response in a RESTful manner.
+In this guide you are going to build a https://grails.apache.org[Grails application] that uses http://gorm.grails.org/latest/mongodb[GORM for MongoDB] to access http://mongodb.org[MongoDB] and produce a JSON response in a RESTful manner.
diff --git a/guides/rest-mongodb/v4/guide/json.adoc b/guides/rest-mongodb/v4/guide/json.adoc
index a497f9bdfb1..5ceeac3ebd6 100644
--- a/guides/rest-mongodb/v4/guide/json.adoc
+++ b/guides/rest-mongodb/v4/guide/json.adoc
@@ -1,4 +1,4 @@
-Grails uses http://views.grails.org[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
+Grails uses https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] to represent render JSON responses. The idea being to continue the philosophy of separating the controller logic from the view logic.
The default view rendered if no specific view is found is `grails-app/views/object/_object.gson`:
@@ -59,4 +59,4 @@ In this trivialized example, we output the currency symbol based on the user's l
[{id:1,"name":"Apple","price":"$2.0"}]
----
-TIP: JSON Views are very flexible, for more information on customizing the output to your needs see http://views.grails.org[the documentation].
+TIP: JSON Views are very flexible, for more information on customizing the output to your needs see https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[the documentation].
diff --git a/guides/rest-mongodb/v4/guide/testing.adoc b/guides/rest-mongodb/v4/guide/testing.adoc
index 59ed34c3ab0..11723faa041 100644
--- a/guides/rest-mongodb/v4/guide/testing.adoc
+++ b/guides/rest-mongodb/v4/guide/testing.adoc
@@ -19,7 +19,7 @@ include::../snippets/src/test/groovy/demo/ProductControllerSpec.groovy[tag=clazz
<1> MongoSpec is an abstract class that will initialise GORM in the setup phase of the specification being executed
<2> Override the `createMongoClient` method of the `MongoSpec` base class. Use something such as https://github.com/fakemongo/fongo[Fongo]; an in-memory java implementation of MongoDB.
-<3> Use the https://testing.grails.org/latest/guide/index.html#unitTestingControllers[grails.testing.web.controllers.ControllerUnitTest] trait to unit test controllers.
+<3> Use the https://grails.apache.org/docs/latest/guide/testing.html[grails.testing.web.controllers.ControllerUnitTest] trait to unit test controllers.
<4> The `setup` method uses the `saveAll` method to save multiple domain classes to serve as test data.
The test performs a search by executing the `search` method, passing appropriate arguments and verifying the JSON written to the response.
diff --git a/guides/server-sent-events/v3/guide/gradleConfig.adoc b/guides/server-sent-events/v3/guide/gradleConfig.adoc
index 325ce94e069..4c477648e0d 100644
--- a/guides/server-sent-events/v3/guide/gradleConfig.adoc
+++ b/guides/server-sent-events/v3/guide/gradleConfig.adoc
@@ -1,4 +1,4 @@
-The first step is to configure the necessary Gradle dependencies. This basically means adding a dependency on the http://plugins.grails.org/plugin/rxjava[RxJava plugin] for Grails in the `build.gradle` file:
+The first step is to configure the necessary Gradle dependencies. This basically means adding a dependency on the https://grails.apache.org/plugins.html[RxJava plugin] for Grails in the `build.gradle` file:
[source,groovy]
----
diff --git a/guides/server-sent-events/v4/guide/gradleConfig.adoc b/guides/server-sent-events/v4/guide/gradleConfig.adoc
index 6d9097d43a5..1a84217256b 100644
--- a/guides/server-sent-events/v4/guide/gradleConfig.adoc
+++ b/guides/server-sent-events/v4/guide/gradleConfig.adoc
@@ -1,4 +1,4 @@
-The first step is to configure the necessary Gradle dependencies. This basically means adding a dependency on the http://plugins.grails.org/plugin/rxjava[RxJava plugin] for Grails and Micronaut `reactivex`in the `build.gradle` file:
+The first step is to configure the necessary Gradle dependencies. This basically means adding a dependency on the https://grails.apache.org/plugins.html[RxJava plugin] for Grails and Micronaut `reactivex`in the `build.gradle` file:
[source,groovy]
----
diff --git a/guides/using-hal-with-json-views/v3/guide/buildingApi.adoc b/guides/using-hal-with-json-views/v3/guide/buildingApi.adoc
index 60dac0a554e..40d1e32ff92 100644
--- a/guides/using-hal-with-json-views/v3/guide/buildingApi.adoc
+++ b/guides/using-hal-with-json-views/v3/guide/buildingApi.adoc
@@ -1 +1 @@
-The default JSON rendered by Grails is a good start, but it doesn't necessarily express the details we want in our public-facing API. http://views.grails.org/latest/[JSON Views] allow us to render our data using Groovy's http://docs.groovy-lang.org/latest/html/gapi/groovy/json/StreamingJsonBuilder.html[`StreamingJsonBuilder`], in a statically-compiled Groovy view. JSON views provide a powerful DSL-based tool for expressing the JSON output from our API.
\ No newline at end of file
+The default JSON rendered by Grails is a good start, but it doesn't necessarily express the details we want in our public-facing API. https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] allow us to render our data using Groovy's http://docs.groovy-lang.org/latest/html/gapi/groovy/json/StreamingJsonBuilder.html[`StreamingJsonBuilder`], in a statically-compiled Groovy view. JSON views provide a powerful DSL-based tool for expressing the JSON output from our API.
\ No newline at end of file
diff --git a/guides/using-hal-with-json-views/v3/guide/gettingStarted.adoc b/guides/using-hal-with-json-views/v3/guide/gettingStarted.adoc
index 33bab3a0d5d..1854f401142 100644
--- a/guides/using-hal-with-json-views/v3/guide/gettingStarted.adoc
+++ b/guides/using-hal-with-json-views/v3/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
-In this guide you are going to explore https://en.wikipedia.org/wiki/Hypertext_Application_Language[HAL] (Hypertext Application Language) support in Grails, using JSON views (provided by the http://views.grails.org/latest/[Grails Views] library).
+In this guide you are going to explore https://en.wikipedia.org/wiki/Hypertext_Application_Language[HAL] (Hypertext Application Language) support in Grails, using JSON views (provided by the https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Grails Views] library).
[quote#wiki, Wikipedia]
____
diff --git a/guides/using-hal-with-json-views/v3/guide/links.adoc b/guides/using-hal-with-json-views/v3/guide/links.adoc
index 3cea11fa66a..cb16b8d7a8b 100644
--- a/guides/using-hal-with-json-views/v3/guide/links.adoc
+++ b/guides/using-hal-with-json-views/v3/guide/links.adoc
@@ -44,7 +44,7 @@ fetch(book._links.author.href).then(function(response) {
});
----
-JSON views implement a Groovy trait http://views.grails.org/latest/api/grails/plugin/json/view/api/HalView.html[`HalView`], which exposes a `hal` helper with several methods for outputting HAL-compliant JSON. One of those is the `links` method:
+JSON views implement a Groovy trait https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[`HalView`], which exposes a `hal` helper with several methods for outputting HAL-compliant JSON. One of those is the `links` method:
[source,groovy]
----
diff --git a/guides/using-hal-with-json-views/v3/guide/runningTheApp.adoc b/guides/using-hal-with-json-views/v3/guide/runningTheApp.adoc
index d13b0a3f21c..f7483faa8db 100644
--- a/guides/using-hal-with-json-views/v3/guide/runningTheApp.adoc
+++ b/guides/using-hal-with-json-views/v3/guide/runningTheApp.adoc
@@ -7,7 +7,7 @@ include::../snippets/../initial/grails-app/domain/com/example/Customer.groovy[in
----
<1> The `@Resource` annotation takes several optional arguments, including a URL endpoint and format options, as well as whether the API should only expose read endpoints
-Adding these annotations to our domain classes gives us a running start to creating our API. See the https://docs.grails.org/latest/guide/webServices.html#domainResources[Grails documentation] for more information on `@Resource`
+Adding these annotations to our domain classes gives us a running start to creating our API. See the https://grails.apache.org/docs/latest/guide/webServices.html#domainResources[Grails documentation] for more information on `@Resource`
include::{commondir}/common-runapp.adoc[]
diff --git a/guides/using-hal-with-json-views/v3/guide/templates.adoc b/guides/using-hal-with-json-views/v3/guide/templates.adoc
index 731c436880a..de4ca17ff73 100644
--- a/guides/using-hal-with-json-views/v3/guide/templates.adoc
+++ b/guides/using-hal-with-json-views/v3/guide/templates.adoc
@@ -18,7 +18,7 @@ include::../snippets/grails-app/views/order/show_v3.gson[]
<1> The `tmpl` helper will resolve a method name to a template in the current view directory - e.g, `tmpl.product` will resolve to `/order/_product.gson`. If you want to access a template from outside the current directory, you can use an absolute path (relative to the `views` directory) as a string: `tmpl."/customer/order"()` will resolve to `grails-app/views/customer/_order.gson`.
-TIP: For more information on using templates in JSON views, see the http://views.grails.org/latest/#_templates[Grails Views documentation].
+TIP: For more information on using templates in JSON views, see the https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Grails Views documentation].
Make a request to `http://localhost:8080/api/orders/1`, and you should see `_links` for each product in the `products` array:
diff --git a/guides/using-hal-with-json-views/v4/guide/buildingApi.adoc b/guides/using-hal-with-json-views/v4/guide/buildingApi.adoc
index 60dac0a554e..40d1e32ff92 100644
--- a/guides/using-hal-with-json-views/v4/guide/buildingApi.adoc
+++ b/guides/using-hal-with-json-views/v4/guide/buildingApi.adoc
@@ -1 +1 @@
-The default JSON rendered by Grails is a good start, but it doesn't necessarily express the details we want in our public-facing API. http://views.grails.org/latest/[JSON Views] allow us to render our data using Groovy's http://docs.groovy-lang.org/latest/html/gapi/groovy/json/StreamingJsonBuilder.html[`StreamingJsonBuilder`], in a statically-compiled Groovy view. JSON views provide a powerful DSL-based tool for expressing the JSON output from our API.
\ No newline at end of file
+The default JSON rendered by Grails is a good start, but it doesn't necessarily express the details we want in our public-facing API. https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[JSON Views] allow us to render our data using Groovy's http://docs.groovy-lang.org/latest/html/gapi/groovy/json/StreamingJsonBuilder.html[`StreamingJsonBuilder`], in a statically-compiled Groovy view. JSON views provide a powerful DSL-based tool for expressing the JSON output from our API.
\ No newline at end of file
diff --git a/guides/using-hal-with-json-views/v4/guide/gettingStarted.adoc b/guides/using-hal-with-json-views/v4/guide/gettingStarted.adoc
index 33bab3a0d5d..1854f401142 100644
--- a/guides/using-hal-with-json-views/v4/guide/gettingStarted.adoc
+++ b/guides/using-hal-with-json-views/v4/guide/gettingStarted.adoc
@@ -1,4 +1,4 @@
-In this guide you are going to explore https://en.wikipedia.org/wiki/Hypertext_Application_Language[HAL] (Hypertext Application Language) support in Grails, using JSON views (provided by the http://views.grails.org/latest/[Grails Views] library).
+In this guide you are going to explore https://en.wikipedia.org/wiki/Hypertext_Application_Language[HAL] (Hypertext Application Language) support in Grails, using JSON views (provided by the https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Grails Views] library).
[quote#wiki, Wikipedia]
____
diff --git a/guides/using-hal-with-json-views/v4/guide/links.adoc b/guides/using-hal-with-json-views/v4/guide/links.adoc
index c51f8a35cea..23b802c6f3f 100644
--- a/guides/using-hal-with-json-views/v4/guide/links.adoc
+++ b/guides/using-hal-with-json-views/v4/guide/links.adoc
@@ -44,7 +44,7 @@ fetch(book._links.author.href).then(function(response) {
});
----
-JSON views implement a Groovy trait http://views.grails.org/latest/api/grails/plugin/json/view/api/HalView.html[`HalView`], which exposes a `hal` helper with several methods for outputting HAL-compliant JSON. One of those is the `links` method:
+JSON views implement a Groovy trait https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[`HalView`], which exposes a `hal` helper with several methods for outputting HAL-compliant JSON. One of those is the `links` method:
[source,groovy]
----
diff --git a/guides/using-hal-with-json-views/v4/guide/runningTheApp.adoc b/guides/using-hal-with-json-views/v4/guide/runningTheApp.adoc
index e962a551dd0..a61a7697994 100644
--- a/guides/using-hal-with-json-views/v4/guide/runningTheApp.adoc
+++ b/guides/using-hal-with-json-views/v4/guide/runningTheApp.adoc
@@ -7,7 +7,7 @@ include::../snippets/../initial/grails-app/domain/com/example/Customer.groovy[in
----
<1> The `@Resource` annotation takes several optional arguments, including a URL endpoint and format options, as well as whether the API should only expose read endpoints
-Adding these annotations to our domain classes gives us a running start to creating our API. See the https://docs.grails.org/latest/guide/webServices.html#domainResources[Grails documentation] for more information on `@Resource`
+Adding these annotations to our domain classes gives us a running start to creating our API. See the https://grails.apache.org/docs/latest/guide/webServices.html#domainResources[Grails documentation] for more information on `@Resource`
include::{commondir}/common-runapp.adoc[]
diff --git a/guides/using-hal-with-json-views/v4/guide/templates.adoc b/guides/using-hal-with-json-views/v4/guide/templates.adoc
index 4216b3612d1..d02e13a4a41 100644
--- a/guides/using-hal-with-json-views/v4/guide/templates.adoc
+++ b/guides/using-hal-with-json-views/v4/guide/templates.adoc
@@ -18,7 +18,7 @@ include::../snippets/grails-app/views/order/show_v3.gson[]
<1> The `tmpl` helper will resolve a method name to a template in the current view directory - e.g, `tmpl.product` will resolve to `/order/_product.gson`. If you want to access a template from outside the current directory, you can use an absolute path (relative to the `views` directory) as a string: `tmpl."/customer/order"()` will resolve to `grails-app/views/customer/_order.gson`.
-TIP: For more information on using templates in JSON views, see the http://views.grails.org/latest/#_templates[Grails Views documentation].
+TIP: For more information on using templates in JSON views, see the https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Grails Views documentation].
Make a request to `http://localhost:8080/api/orders/1`, and you should see `_links` for each product in the `products` array:
diff --git a/guides/using-the-vue-profile/v3/guide/generateTheApp.adoc b/guides/using-the-vue-profile/v3/guide/generateTheApp.adoc
index 509526d63a4..3bae50c306b 100644
--- a/guides/using-the-vue-profile/v3/guide/generateTheApp.adoc
+++ b/guides/using-the-vue-profile/v3/guide/generateTheApp.adoc
@@ -25,7 +25,7 @@ drwxr-xr-x 8 zak staff 272 Nov 1 13:12 server
-rw-r--r-- 1 zak staff 26 Nov 1 13:10 settings.gradle
----
-The `server` project is our Grails application. The profile will generate a Grails app using the `rest-api` profile, which provides support for creating domain classes as restful resources, http://docs.grails.org/snapshot/guide/single.html#cors[CORS enabled by default], as well as JSON and Markup views.
+The `server` project is our Grails application. The profile will generate a Grails app using the `rest-api` profile, which provides support for creating domain classes as restful resources, https://grails.apache.org/docs/snapshot/guide/single.html#cors[CORS enabled by default], as well as JSON and Markup views.
`client` is our Vue app.
diff --git a/guides/using-the-vue-profile/v4/guide/generateTheApp.adoc b/guides/using-the-vue-profile/v4/guide/generateTheApp.adoc
index 1f0403a80b1..718d1e8d7ac 100644
--- a/guides/using-the-vue-profile/v4/guide/generateTheApp.adoc
+++ b/guides/using-the-vue-profile/v4/guide/generateTheApp.adoc
@@ -25,7 +25,7 @@ drwxr-xr-x 8 zak staff 272 Nov 1 13:12 server
-rw-r--r-- 1 zak staff 26 Nov 1 13:10 settings.gradle
----
-The `server` project is our Grails application. The profile will generate a Grails app using the `rest-api` profile, which provides support for creating domain classes as restful resources, http://docs.grails.org/snapshot/guide/single.html#cors[CORS enabled by default], as well as JSON and Markup views.
+The `server` project is our Grails application. The profile will generate a Grails app using the `rest-api` profile, which provides support for creating domain classes as restful resources, https://grails.apache.org/docs/snapshot/guide/single.html#cors[CORS enabled by default], as well as JSON and Markup views.
`client` is our Vue app.
diff --git a/guides/vaadin-grails/v4/guide/aboutVaadin.adoc b/guides/vaadin-grails/v4/guide/aboutVaadin.adoc
index 10191934602..39c727e3c1a 100644
--- a/guides/vaadin-grails/v4/guide/aboutVaadin.adoc
+++ b/guides/vaadin-grails/v4/guide/aboutVaadin.adoc
@@ -10,7 +10,7 @@ image::charts-on-mobile-and-desktop.png[]
TIP: The Vaadin 8 Grails profile allows you mix Vaadin endpoints and traditional Grails endpoints.
On the one hand, we are going to have endpoints which will be handled by Grails Controllers. They will render HTML, JSON or XML using
-http://gsp.grails.org[GSP] or http://views.grails.org[Grails Views].
+https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp[GSP] or https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson[Grails Views].
On the other hand, we are going to have Vaadin endpoints. We will develop the UI using Java or Groovy, and we will connect to the Grails service layer directly.
diff --git a/guides/vaadin-grails/v4/guide/profile.adoc b/guides/vaadin-grails/v4/guide/profile.adoc
index 9723e3574ff..619e8649ea9 100644
--- a/guides/vaadin-grails/v4/guide/profile.adoc
+++ b/guides/vaadin-grails/v4/guide/profile.adoc
@@ -7,4 +7,4 @@ grails create-app demo --profile me.przepiora.vaadin-grails:web-vaadin8:0.3
We supply to the `create-app` command the https://github.com/macprzepiora/web-vaadin8[Vaadin 8 Grails Profile]'s coordinates.
-With the use of http://docs.grails.org/latest/guide/single.html#profiles[application profiles], Grails allows you to build modern web applications. There are profiles to facilitate the construction of REST APIs or Web applications with a Javascript front-end (Angular, REACT) or Vaadin apps.
\ No newline at end of file
+With the use of https://grails.apache.org/docs/latest/guide/single.html#profiles[application profiles], Grails allows you to build modern web applications. There are profiles to facilitate the construction of REST APIs or Web applications with a Javascript front-end (Angular, REACT) or Vaadin apps.
\ No newline at end of file
diff --git a/posts/2016-05-28.md b/posts/2016-05-28.md
index 514f2958678..659d5b9479a 100644
--- a/posts/2016-05-28.md
+++ b/posts/2016-05-28.md
@@ -501,7 +501,7 @@ JSX allows us to write Javascript expressions bound by curly braces, supports na
Now that we have our React app integrated into our Grails project and served up via the asset pipeline, we can start to build out our application and write components that consume our restful API. Because React is a view library, it doesn’t offer specialized features for communicating with a restful API. Developers are encouraged to use native Javascript APIs or other libraries to supply this functionality. The example project from this article uses the [fetch API](https://developer.mozi [...]
-The app allows a user to create new todo lists and add new todo items to them. All changes are saved to the mongo database. It also makes use of [JSON Views](https://views.grails.org/latest/) to customize the JSON output from our endpoints.
+The app allows a user to create new todo lists and add new todo items to them. All changes are saved to the mongo database. It also makes use of [JSON Views](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson) to customize the JSON output from our endpoints.
No update or delete functions are provided at this time. Those features are left as an exercise to the reader.
diff --git a/posts/2016-05-31.md b/posts/2016-05-31.md
index f021a1edda4..38c0b9069e3 100644
--- a/posts/2016-05-31.md
+++ b/posts/2016-05-31.md
@@ -29,7 +29,7 @@ Grails 3.2 features support for scaffolding of AngularJS 1.x applications (suppo
JSON views, a feature introduced in Grails 3.1, have been drastically improved with support for template inheritance, global templates, extended HAL support and more.
-See the [documentation for the 1.1 milestone 2 version](https://views.grails.org/1.1.0.M2/#_version_history) of the JSON views plugin for more information.
+See the [documentation for the 1.1 milestone 2 version](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson) of the JSON views plugin for more information.
## What's Still Coming?
diff --git a/posts/2016-09-28.md b/posts/2016-09-28.md
index 5475e91c9be..ccfd7b9a9f2 100644
--- a/posts/2016-09-28.md
+++ b/posts/2016-09-28.md
@@ -44,7 +44,7 @@ For the first release of RxGORM, implementations for [MongoDB](https://gorm.grai
Grails 3.2 bundles all of the goodness of GORM 6, plus a whole bunch of new features in the core framework:
* RxJava support via a [new plugin](/plugins.html#plugin/rxjava).
-* Improved [JSON View](https://views.grails.org/) support.
+* Improved [JSON View](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson) support.
* AngularJS scaffolding
* REST improvements
* Latest and greatest libraries (Spring Boot 1.4, Gradle 3.0, etc.)
diff --git a/posts/2017-04-02.md b/posts/2017-04-02.md
index 11793486d76..48315c7c9cd 100644
--- a/posts/2017-04-02.md
+++ b/posts/2017-04-02.md
@@ -38,7 +38,7 @@ info.app.grailsVersion=3.2.5
This info primarily comes from `build.gradle` and `gradle.properties` (the curious can check out the source code in [grails-core](https://github.com/apache/grails-core/blob/6c85ec239aa8cc4a9f646bb345c70c327ddb2dbc/grails-gradle-plugin/src/main/groovy/org/grails/gradle/plugin/core/GrailsGradlePlugin.groovy#L179)). This file will be part of your final application when you build your `.jar` or `.war` file.
-In a `.gsp`, this information is available by using the meta tag like this: (see the [tag](https://gsp.grails.org/latest/guide/index.html#tags) documentation).
+In a `.gsp`, this information is available by using the meta tag like this: (see the [tag](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gsp) documentation).
## Adding More Information to `grails.build.info`
diff --git a/posts/2017-07-26.md b/posts/2017-07-26.md
index 91071db74d7..9bb89c28ee2 100644
--- a/posts/2017-07-26.md
+++ b/posts/2017-07-26.md
@@ -19,8 +19,8 @@ Grails 3.3 includes a number of significant improvements, most notably to GORM w
GORM 6.1 includes some real breakthrough innovations, including [Data Services](https://gorm.grails.org/6.1.x/hibernate/manual/index.html#dataServices) that allow you to define interfaces that are automatically implemented and work seamlessly with GORM's multi-tenancy features.
-Other highlights of Grails 3.3 include the new [EventBus](https://async.grails.org/latest/guide/index.html#events) abstraction which integrates with existing reactive libraries such as RxJava. Events are also for the first time transaction aware so that consumers are only notified if the surrounding transaction is successful, which simplifies code greatly.
+Other highlights of Grails 3.3 include the new [EventBus](https://grails.apache.org/docs/latest/guide/async.html) abstraction which integrates with existing reactive libraries such as RxJava. Events are also for the first time transaction aware so that consumers are only notified if the surrounding transaction is successful, which simplifies code greatly.
-Overall there is an abundance of new features and improvements that developers will be able to take advantage of, from the [new testing framework](https://testing.grails.org/) to improvemments to [JSON Views](https://views.grails.org/latest/).
+Overall there is an abundance of new features and improvements that developers will be able to take advantage of, from the [new testing framework](https://grails.apache.org/docs/latest/guide/testing.html) to improvemments to [JSON Views](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson).
All of these new features and more are covered in the [What's New guide](https://grails.apache.org/docs/3.3.x/guide/introduction.html#whatsNew). Thanks to the Grails community who contributed greatly to making the release a success and we look forward [to your feedback](https://github.com/apache/grails-core/issues)!
diff --git a/posts/2018-05-24.md b/posts/2018-05-24.md
index 8455646e827..80bd488b703 100644
--- a/posts/2018-05-24.md
+++ b/posts/2018-05-24.md
@@ -21,7 +21,7 @@ This blog will highlight some mock logging techniques and when to use them.
First let's get the obvious out of the way for clarity. If you are not concerned about testing how logs operate in your application, there is no reason to worry about mocking loggers in Grails apps.
-Since the logger is already present in Grails controllers, services, and domain objects there is no need to mock the logger when running unit tests. When a unit test is run with [Grails Testing Support](https://testing.grails.org/latest/guide/index.html), the logger will execute just as in does in production mode. In this scenario, we can say the logger as already "mocked" for the purpose of focusing on the [Class Under Test](https://wiki.c2.com/?ClassUnderTest). This is distinct from th [...]
+Since the logger is already present in Grails controllers, services, and domain objects there is no need to mock the logger when running unit tests. When a unit test is run with [Grails Testing Support](https://grails.apache.org/docs/latest/guide/testing.html), the logger will execute just as in does in production mode. In this scenario, we can say the logger as already "mocked" for the purpose of focusing on the [Class Under Test](https://wiki.c2.com/?ClassUnderTest). This is distinct f [...]
## Verify Logging with Tests
diff --git a/templates/partials/site-header.html b/templates/partials/site-header.html
index 34eb1df69f0..500c77c7a4a 100644
--- a/templates/partials/site-header.html
+++ b/templates/partials/site-header.html
@@ -17,7 +17,7 @@
<ul>
<li><a href='https://grails.apache.org/documentation.html'>Documentation</a></li>
<li><a href='https://grails.apache.org/download.html'>Download</a></li>
- <li><a href='https://plugins.grails.org'>Plugins</a></li>
+ <li><a href='https://grails.apache.org/plugins.html'>Plugins</a></li>
<li><a href='https://grails.apache.org/guides'>Guides</a></li>
<li><a href='https://grails.apache.org/faq.html'>FAQ</a></li>
<li><a href='https://grails.apache.org/support.html'>Support</a></li>