Merge pull request #415 from sanjana2505006/feature/fix-legacy-urls

Cleanup Old Grails.org and GitHub.io URLs

Author: sbglasius

posts/2015-03-01.md

@@ -86,7 +86,7 @@ class FirstInterceptorSpec extends Specification {
 
 ## The Interceptor Trait
 
-Grails 3 takes advantage of Groovy's powerful and flexible support for traits in many places. All interceptors are automatically made to implement the [grails.artefact.Interceptor](https://grails.github.io/legacy-grails-doc/3.0.x/api/grails/artefact/Interceptor.html) trait so all of the methods and properties defined by that trait and all of the methods and properties defined by traits which that trait extends are all available inside of an interceptor. This provides easy access to attributes like `grailsApplication`, `params`, `request`, `session` and others. The trait also provides access to methods like `redirect` and `render`.
+Grails 3 takes advantage of Groovy's powerful and flexible support for traits in many places. All interceptors are automatically made to implement the [grails.artefact.Interceptor](https://grails.apache.org/docs/3.0.x/api/grails/artefact/Interceptor.html) trait so all of the methods and properties defined by that trait and all of the methods and properties defined by traits which that trait extends are all available inside of an interceptor. This provides easy access to attributes like `grailsApplication`, `params`, `request`, `session` and others. The trait also provides access to methods like `redirect` and `render`.
 
 ## Matching Requests
 
@@ -138,7 +138,7 @@ class FirstInterceptor {
 }
 ```
 
-The `match` and `matchAll` methods in an intereceptor each return an instance of [grails.interceptors.Matcher](https://grails.github.io/grails-doc/3.0.x/api/grails/interceptors/Matcher.html). Most of the methods in `Matcher` also return the `Matcher` which allows for method chaining as shown above with `matchAll().excludes(controller: 'auth')`.
+The `match` and `matchAll` methods in an intereceptor each return an instance of [grails.interceptors.Matcher](https://grails.apache.org/docs/3.0.x/api/grails/interceptors/Matcher.html). Most of the methods in `Matcher` also return the `Matcher` which allows for method chaining as shown above with `matchAll().excludes(controller: 'auth')`.
 
 Care should be taken to narrow the group of requests that an interceptor is applied to. Keep in mind that whatever logic is contained in an interceptor is being engaged for all of the requests that the interceptor matches.
 
@@ -246,7 +246,7 @@ The framework offers flexibility around this such that if you would like to sepa
 
 All interceptors are configured as beans in the Spring application context and are configured to be autowired by name. This means that just like other Grails artifacts, an interceptor may define a property with a name that matches a bean name and that property will be initialized using standard Spring dependency injection.
 
-In addition to participating in dependency injection, because interceptors are Spring beans they participate in all of the standard Spring bean management handling. For example, if an interceptor wanted access to the application's configuration, the intereceptor class could implement the [grails.core.support.GrailsConfigurationAware](https://grails.github.io/grails-doc/3.0.x/api/grails/core/support/GrailsConfigurationAware.html) interface.
+In addition to participating in dependency injection, because interceptors are Spring beans they participate in all of the standard Spring bean management handling. For example, if an interceptor wanted access to the application's configuration, the intereceptor class could implement the [grails.core.support.GrailsConfigurationAware](https://grails.apache.org/docs/3.0.x/api/grails/core/support/GrailsConfigurationAware.html) interface.
 
 ```groovy
 package demo

posts/2016-04-13.md

@@ -74,4 +74,4 @@ The following paths are searched:
 
 The content type (defined by either the `ACCEPT` header or file extension in the URI) is taken into account to allow different formats for the same view.
 
-For more detail, see [the official documentation](https://grails.github.io/grails-views/latest/).
+For more detail, see [the official documentation](https://grails.apache.org/docs/latest/guide/theWebLayer.html#gson).

posts/2023-07-25-introducing-grails-6.md

@@ -30,7 +30,7 @@ Grails 6 incorporates the latest updates of Spring 5.3.28 and Spring Boot 2.7.12
 Grails 6 now provides support for the latest Gradle version, 7.6.1, offering developers a more efficient and robust build automation tool. Gradle 7.6.1 brings with it various improvements, enhanced performance, and additional features, further streamlining the development process and ensuring compatibility with the latest libraries and dependencies.
 
 ## Introducing the New Grails Forge:
-**Grails 6 not only embraces modern Java and the latest Spring and Spring Boot updates but also introduces the New Grails Forge UI, revolutionizing the web development experience for creating and managing Grails projects.** With [the New Grails Forge UI](https://grails.github.io/grails-forge-ui/), developers can enjoy a modern and efficient user interface with simplified project creation, intuitive navigation, real-time feedback and validation, visual dependency management, enhanced plugin integration, project customization, built-in best practices, and responsive design. This intuitive UI streamlines the development process, making it easier for developers to set up new Grails projects and manage existing ones.
+**Grails 6 not only embraces modern Java and the latest Spring and Spring Boot updates but also introduces the New Grails Forge UI, revolutionizing the web development experience for creating and managing Grails projects.** With [the New Grails Forge UI](https://apache.github.io/grails-forge-ui/), developers can enjoy a modern and efficient user interface with simplified project creation, intuitive navigation, real-time feedback and validation, visual dependency management, enhanced plugin integration, project customization, built-in best practices, and responsive design. This intuitive UI streamlines the development process, making it easier for developers to set up new Grails projects and manage existing ones.
 
 ## Enhanced Integration of the Micronaut framework with Grails:
 The Grails framework has long provided integration with the Micronaut framework, fostering seamless collaboration between the two Frameworks. With Grails 6, we are proud to announce further improvements in this integration, enhancing the developer experience with each major release. Developers can now enjoy even better Micronaut integration, promoting code reuse and reducing redundancy between Grails and Micronaut components. For instance, developers can easily inject Micronaut beans into Grails services, controllers, and other components, gaining access to the Micronaut framework’s extensive ecosystem of features and functionalities.