5.5 Building with Gradle
5.5.1 Defining Dependencies with Gradle
5.5.1 Defining Dependencies with Gradle
runtime 'org.grails.plugins:asset-pipeline' runtime 'org.grails.plugins:scaffolding' - testCompile 'org.grails:grails-plugin-testing' + testCompile "org.grails:grails-gorm-testing-support" + testCompile "org.grails:grails-web-testing-support" testCompile 'org.grails.plugins:geb' // Note: It is recommended to update to a more robust driver (Chrome, Firefox etc.) @@ -747,7 +748,7 @@5.5.1 Defining Dependencies with Gradle
5.5.2 Working with Gradle Tasks
5.5.2 Working with Gradle Tasks
test-app
check
test-app --unit
test
5.5.2 Working with Gradle Tasks
5.5.3 Grails plugins for Gradle
4 Configuration
-Version: 4.0.13
+Version: 5.0.1
Table of Contents
4 Configuration
4 Configuration
4.1 Basic Configuration
4.1 Basic Configuration
Accessing Configuration with GrailsApplication
If you want to read runtime configuration settings, i.e. those defined in application.yml, use the grailsApplication object, which is available as a variable in controllers and tag libraries:
If you want to read runtime configuration settings, i.e. those defined in application.yml, use the grailsApplication object, which is available as a variable in controllers and tag libraries:
Accessing Configuration
The config property of the grailsApplication object is an instance of the Config interface and provides a number of useful methods to read the configuration of the application.
The config property of the grailsApplication object is an instance of the Config interface and provides a number of useful methods to read the configuration of the application.
In particular, the getProperty method (seen above) is useful for efficiently retrieving configuration properties, while specifying the property type (the default type is String) and/or providing a default fallback value.
Accessing Configuration
Notice that the Config instance is a merged configuration based on Spring’s PropertySource concept and reads configuration from the environment, system properties and the local application configuration merging them into a single object.
Notice that the Config instance is a merged configuration based on Spring’s PropertySource concept and reads configuration from the environment, system properties and the local application configuration merging them into a single object.
GrailsApplication can be easily injected into services and other Grails artifacts:
Accessing Configuration
GrailsConfigurationAware Interface
-Accessing configuration dynamically at runtime can have a small effect on application performance. An alternative approach is to implement the GrailsConfigurationAware interface, which provides a setConfiguration method that accepts the application configuration as a parameter when the class is initialized. You can then assign relevant configuration properties to instance properties on the class for later usage.
+Accessing configuration dynamically at runtime can have a small effect on application performance. An alternative approach is to implement the GrailsConfigurationAware interface, which provides a setConfiguration method that accepts the application configuration as a parameter when the class is initialized. You can then assign relevant configuration properties to instance properties on the class for later usage.
The Config instance has the same properties and usage as the injected GrailsApplication config object. Here is the service class from the previous example, using GrailsConfigurationAware instead of injecting GrailsApplication:
@@ -410,7 +410,7 @@ GrailsConfigurationAware Interface<
Spring Value Annotation
-You can use Spring’s Value annotation to inject configuration values:
+You can use Spring’s Value annotation to inject configuration values:
@@ -447,7 +447,7 @@ Spring Value Annotation
4.1.1 Options for the YML format Config
-
@@ -496,7 +496,7 @@ Using system properties
External configuration
Grails will read application.(properties|yml) from the ./config or the current directory by default.
-As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.1.x/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
+As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.5.2/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
@@ -504,7 +504,7 @@ External configuration
4.1.2 Built in options
-
@@ -536,7 +536,7 @@ Runtime settings
grails.mime.types - A map of supported mime types used for Content Negotiation.
-grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
+grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
grails.views.gsp.sitemesh.preprocess - Determines whether SiteMesh preprocessing happens. Disabling this slows down page rendering, but if you need SiteMesh to parse the generated HTML from a GSP view then disabling it is the right option. Don’t worry if you don’t understand this advanced property: leave it set to true.
@@ -552,36 +552,24 @@ Runtime settings
4.1.3 Logging
-
-Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.groovy file.
-
-
-
-
-
-
-
-
-If you prefer XML you can replace the logback.groovy file with a logback.xml file instead.
-
-
-
+Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.xml file.
-For more information on configuring logging refer to the Logback documentation on the subject.
+For more information on configuring logging refer to the Logback documentation on the subject.
4.1.3.1 Logger Names
-
@@ -699,7 +687,7 @@ 4.1.3.1 Logger Names
4.1.3.2 Masking Request Parameters From Stacktrace Logs
-
@@ -738,7 +726,7 @@ 4.1.3.2 Masking Request Para
4.1.3.3 External Configuration File
-
@@ -751,21 +739,21 @@ 4.1.3.3 External Configuration File
grails-app/conf/application.yml
logging:
- config: /Users/me/config/logback.groovy
+ config: /Users/me/config/logback.xml
Alternatively, you can supply the configuration file location with a system property:
-$ ./gradlew -Dlogging.config=/Users/me/config/logback.groovy bootRun
+$ ./gradlew -Dlogging.config=/Users/me/config/logback.xml bootRun
Or, you could use an environment variable:
-$ export LOGGING_CONFIG=/Users/me/config/logback.groovy
+$ export LOGGING_CONFIG=/Users/me/config/logback.xml
$ ./gradlew bootRun
@@ -774,7 +762,7 @@ 4.1.3.3 External Configuration File
4.1.4 GORM
-
@@ -817,7 +805,7 @@ 4.1.4 GORM
4.1.5 Configuring an HTTP proxy
-
@@ -857,7 +845,7 @@ 4.1.5 Configuring an HTTP proxy
4.2 The Application Class
-
@@ -867,14 +855,14 @@ 4.2 The Application Class
Every new Grails application features an Application class within the grails-app/init directory.
-The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
+The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
4.2.1 Executing the Application Class
-
@@ -903,7 +891,7 @@ 4.2.1 Executing the Application Class
4.2.2 Customizing the Application Class
-
@@ -933,7 +921,7 @@ Customizing Scanning
Registering Additional Beans
-The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
+The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
@@ -953,14 +941,14 @@ Registering Additional Beans
4.2.3 The Application LifeCycle
-
-The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
+The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
This means that the Application class can be used to perform the same functions as a plugin. You can override the regular plugins hooks such as doWithSpring, doWithApplicationContext and so on by overriding the appropriate method:
@@ -984,7 +972,7 @@ 4.2.3 The Application LifeCycle
4.3 Environments
-
@@ -1087,7 +1075,7 @@ Packaging and Running
Programmatic Environment Detection
-Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
+Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
@@ -1150,7 +1138,7 @@ Generic Per Environment Execution4.4 The DataSource
-
@@ -1393,7 +1381,7 @@ More on dbCreate
4.4.1 DataSources and Environments
-
@@ -1429,7 +1417,7 @@ 4.4.1 DataSources and Environments
4.4.2 Automatic Database Migration
-
@@ -1481,7 +1469,7 @@ 4.4.2 Automatic Database Migration
4.4.3 Transaction-aware DataSource Proxy
-
@@ -1498,7 +1486,7 @@ 4.4.3 Transaction-aware DataSource Prox
4.4.4 Database Console
-
@@ -1508,14 +1496,14 @@ 4.4.4 Database Console
The H2 database console is a convenient feature of H2 that provides a web-based interface to any database that you have a JDBC driver for, and it’s very useful to view the database you’re developing against. It’s especially useful when running against an in-memory database.
-You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
+You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
4.4.5 Multiple Datasources
-
@@ -1819,7 +1807,7 @@ Transactions across multiple
The BE1PC implementation was added in Grails 2.3.6. . Before this change additional datasources didn’t take part in transactions initiated in Grails. The transactions in additional datasources were basically in auto commit mode. In some cases this might be the wanted behavior. One reason might be performance: on the start of each new transaction, the BE1PC transaction manager creates a new transaction to each datasource. It’s possible to leave an additional datasource out of the BE1PC transaction manager by setting transactional = false in the respective configuration block of the additional dataSource. Datasources with readOnly = true will also be left out of the chained transaction manager (since 2.3.7).
-By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
+By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
You can exclude transaction manager beans from the BE1PC implementation with this configuration option:
@@ -1843,7 +1831,7 @@ XA and Two-phase Commit
When the Best Efforts 1PC pattern isn’t suitable for handling transactions across multiple transactional resources (not only datasources), there are several options available for adding XA/2PC support to Grails applications.
-The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
+The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
@@ -1851,7 +1839,7 @@ XA and Two-phase Commit
4.5 Versioning
-
@@ -1860,7 +1848,7 @@ 4.5 Versioning
Detecting Versions at Runtime
-You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
+You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
@@ -1891,7 +1879,7 @@ Detecting Versions at Runtime
4.6 Dependency Resolution
-
@@ -1904,7 +1892,7 @@ 4.6 Dependency Resolution
-
+
diff --git a/snapshot/guide/contributing.html b/snapshot/guide/contributing.html
index 7f16a4feebe..cd5674d6586 100644
--- a/snapshot/guide/contributing.html
+++ b/snapshot/guide/contributing.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 22 Contributing to Grails 4.0.13
+ 22 Contributing to Grails 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -133,7 +133,7 @@
22 Contributing to Grails
- Version: 4.0.13
+ Version: 5.0.1
@@ -160,7 +160,7 @@ Table of Contents
22 Contributing to Grails
-
@@ -174,7 +174,7 @@ 22 Contributing to Grails
22.1 Report Issues in Github's issue tracker
-
@@ -203,7 +203,7 @@ Reviewing issues
22.2 Build From Source and Run Tests
-
@@ -378,7 +378,7 @@ Debugging Grails or a Grails
22.3 Submit Patches to Grails Core
-
@@ -497,7 +497,7 @@ Say what your pull request is for22.4 Submit Patches to Grails Documentation
-
diff --git a/snapshot/guide/deployment.html b/snapshot/guide/deployment.html
index 8b8cb35a554..0e4a2086f42 100644
--- a/snapshot/guide/deployment.html
+++ b/snapshot/guide/deployment.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 21 Deployment 4.0.13
+ 21 Deployment 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -135,7 +135,7 @@
21 Deployment
- Version: 4.0.13
+ Version: 5.0.1
@@ -159,7 +159,7 @@ Table of Contents
21 Deployment
-
@@ -173,7 +173,7 @@ 21 Deployment
21.1 Standalone
-
@@ -250,7 +250,7 @@ A TAR/ZIP distribution
21.2 Container Deployment (e.g. Tomcat)
-
@@ -297,7 +297,7 @@ Application servers
21.3 Deployment Configuration Tasks
-
@@ -341,10 +341,13 @@ Settin
diff --git a/snapshot/guide/gettingStarted.html b/snapshot/guide/gettingStarted.html
index e50b744c209..50a1febd656 100644
--- a/snapshot/guide/gettingStarted.html
+++ b/snapshot/guide/gettingStarted.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 2 Getting Started 4.0.13
+ 2 Getting Started 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -128,14 +128,14 @@
(Quick Reference)
-
+
2 Getting Started
- Version: 4.0.13
+ Version: 5.0.1
@@ -189,7 +189,7 @@ Table of Contents
2 Getting Started
-
@@ -201,20 +201,20 @@ 2 Getting Started
2.1 Installation Requirements
-
-Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
+Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
-On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
@@ -239,7 +239,7 @@ 2.1 Installation Requirements
2.2 Downloading and Installing
-
@@ -271,7 +271,7 @@ Install with SDKMAN
-sdk install grails 4.0.13
+sdk install grails 5.0.1
@@ -307,12 +307,20 @@ Unix/Linux
-
-===Windows
-** Copy the path to the bin directory inside the grails folder you have downloaded, for example,
----
-C:/path_to_grails/bin
----
+
+
+Windows
+
+
+-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
+
+
+
+C:/path_to_grails/bin
+
@@ -321,11 +329,11 @@ Unix/Linux
-
-
-Start + R
+
+
+Start + R
+
-
-
@@ -341,7 +349,7 @@
Unix/Linux
-Grails version: 4.0.13
+Grails version: 5.0.1
@@ -352,7 +360,7 @@ Unix/Linux
2.3 Creating an Application
-
@@ -387,7 +395,7 @@ 2.3 Creating an Application
2.4 A Hello World Example
-
@@ -517,7 +525,7 @@ 2.4 A Hello World Example
2.5 Using Interactive Mode
-
@@ -539,7 +547,7 @@ 2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
-
@@ -548,7 +556,7 @@ 2.6 Getting Set Up in an IDE
IntelliJ IDEA
-IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@ IntelliJ IDEA
GrailsConfigurationAware Interface
Accessing configuration dynamically at runtime can have a small effect on application performance. An alternative approach is to implement the GrailsConfigurationAware interface, which provides a setConfiguration method that accepts the application configuration as a parameter when the class is initialized. You can then assign relevant configuration properties to instance properties on the class for later usage.
Accessing configuration dynamically at runtime can have a small effect on application performance. An alternative approach is to implement the GrailsConfigurationAware interface, which provides a setConfiguration method that accepts the application configuration as a parameter when the class is initialized. You can then assign relevant configuration properties to instance properties on the class for later usage.
The Config instance has the same properties and usage as the injected GrailsApplication config object. Here is the service class from the previous example, using GrailsConfigurationAware instead of injecting GrailsApplication:
GrailsConfigurationAware Interface<
Spring Value Annotation
-You can use Spring’s Value annotation to inject configuration values:
+You can use Spring’s Value annotation to inject configuration values:
@@ -447,7 +447,7 @@ Spring Value Annotation
4.1.1 Options for the YML format Config
-
@@ -496,7 +496,7 @@ Using system properties
External configuration
Grails will read application.(properties|yml) from the ./config or the current directory by default.
-As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.1.x/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
+As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.5.2/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
@@ -504,7 +504,7 @@ External configuration
4.1.2 Built in options
-
@@ -536,7 +536,7 @@ Runtime settings
grails.mime.types - A map of supported mime types used for Content Negotiation.
-grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
+grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
grails.views.gsp.sitemesh.preprocess - Determines whether SiteMesh preprocessing happens. Disabling this slows down page rendering, but if you need SiteMesh to parse the generated HTML from a GSP view then disabling it is the right option. Don’t worry if you don’t understand this advanced property: leave it set to true.
@@ -552,36 +552,24 @@ Runtime settings
4.1.3 Logging
-
-Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.groovy file.
-
-
-
-
-
-
-
-
-If you prefer XML you can replace the logback.groovy file with a logback.xml file instead.
-
-
-
+Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.xml file.
-For more information on configuring logging refer to the Logback documentation on the subject.
+For more information on configuring logging refer to the Logback documentation on the subject.
4.1.3.1 Logger Names
-
@@ -699,7 +687,7 @@ 4.1.3.1 Logger Names
4.1.3.2 Masking Request Parameters From Stacktrace Logs
-
@@ -738,7 +726,7 @@ 4.1.3.2 Masking Request Para
4.1.3.3 External Configuration File
-
@@ -751,21 +739,21 @@ 4.1.3.3 External Configuration File
grails-app/conf/application.yml
logging:
- config: /Users/me/config/logback.groovy
+ config: /Users/me/config/logback.xml
Alternatively, you can supply the configuration file location with a system property:
-$ ./gradlew -Dlogging.config=/Users/me/config/logback.groovy bootRun
+$ ./gradlew -Dlogging.config=/Users/me/config/logback.xml bootRun
Or, you could use an environment variable:
-$ export LOGGING_CONFIG=/Users/me/config/logback.groovy
+$ export LOGGING_CONFIG=/Users/me/config/logback.xml
$ ./gradlew bootRun
@@ -774,7 +762,7 @@ 4.1.3.3 External Configuration File
4.1.4 GORM
-
@@ -817,7 +805,7 @@ 4.1.4 GORM
4.1.5 Configuring an HTTP proxy
-
@@ -857,7 +845,7 @@ 4.1.5 Configuring an HTTP proxy
4.2 The Application Class
-
@@ -867,14 +855,14 @@ 4.2 The Application Class
Every new Grails application features an Application class within the grails-app/init directory.
-The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
+The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
4.2.1 Executing the Application Class
-
@@ -903,7 +891,7 @@ 4.2.1 Executing the Application Class
4.2.2 Customizing the Application Class
-
@@ -933,7 +921,7 @@ Customizing Scanning
Registering Additional Beans
-The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
+The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
@@ -953,14 +941,14 @@ Registering Additional Beans
4.2.3 The Application LifeCycle
-
-The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
+The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
This means that the Application class can be used to perform the same functions as a plugin. You can override the regular plugins hooks such as doWithSpring, doWithApplicationContext and so on by overriding the appropriate method:
@@ -984,7 +972,7 @@ 4.2.3 The Application LifeCycle
4.3 Environments
-
@@ -1087,7 +1075,7 @@ Packaging and Running
Programmatic Environment Detection
-Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
+Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
@@ -1150,7 +1138,7 @@ Generic Per Environment Execution4.4 The DataSource
-
@@ -1393,7 +1381,7 @@ More on dbCreate
4.4.1 DataSources and Environments
-
@@ -1429,7 +1417,7 @@ 4.4.1 DataSources and Environments
4.4.2 Automatic Database Migration
-
@@ -1481,7 +1469,7 @@ 4.4.2 Automatic Database Migration
4.4.3 Transaction-aware DataSource Proxy
-
@@ -1498,7 +1486,7 @@ 4.4.3 Transaction-aware DataSource Prox
4.4.4 Database Console
-
@@ -1508,14 +1496,14 @@ 4.4.4 Database Console
The H2 database console is a convenient feature of H2 that provides a web-based interface to any database that you have a JDBC driver for, and it’s very useful to view the database you’re developing against. It’s especially useful when running against an in-memory database.
-You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
+You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
4.4.5 Multiple Datasources
-
@@ -1819,7 +1807,7 @@ Transactions across multiple
The BE1PC implementation was added in Grails 2.3.6. . Before this change additional datasources didn’t take part in transactions initiated in Grails. The transactions in additional datasources were basically in auto commit mode. In some cases this might be the wanted behavior. One reason might be performance: on the start of each new transaction, the BE1PC transaction manager creates a new transaction to each datasource. It’s possible to leave an additional datasource out of the BE1PC transaction manager by setting transactional = false in the respective configuration block of the additional dataSource. Datasources with readOnly = true will also be left out of the chained transaction manager (since 2.3.7).
-By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
+By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
You can exclude transaction manager beans from the BE1PC implementation with this configuration option:
@@ -1843,7 +1831,7 @@ XA and Two-phase Commit
When the Best Efforts 1PC pattern isn’t suitable for handling transactions across multiple transactional resources (not only datasources), there are several options available for adding XA/2PC support to Grails applications.
-The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
+The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
@@ -1851,7 +1839,7 @@ XA and Two-phase Commit
4.5 Versioning
-
@@ -1860,7 +1848,7 @@ 4.5 Versioning
Detecting Versions at Runtime
-You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
+You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
@@ -1891,7 +1879,7 @@ Detecting Versions at Runtime
4.6 Dependency Resolution
-
@@ -1904,7 +1892,7 @@ 4.6 Dependency Resolution
-
+
diff --git a/snapshot/guide/contributing.html b/snapshot/guide/contributing.html
index 7f16a4feebe..cd5674d6586 100644
--- a/snapshot/guide/contributing.html
+++ b/snapshot/guide/contributing.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 22 Contributing to Grails 4.0.13
+ 22 Contributing to Grails 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -133,7 +133,7 @@
22 Contributing to Grails
- Version: 4.0.13
+ Version: 5.0.1
@@ -160,7 +160,7 @@ Table of Contents
22 Contributing to Grails
-
@@ -174,7 +174,7 @@ 22 Contributing to Grails
22.1 Report Issues in Github's issue tracker
-
@@ -203,7 +203,7 @@ Reviewing issues
22.2 Build From Source and Run Tests
-
@@ -378,7 +378,7 @@ Debugging Grails or a Grails
22.3 Submit Patches to Grails Core
-
@@ -497,7 +497,7 @@ Say what your pull request is for22.4 Submit Patches to Grails Documentation
-
diff --git a/snapshot/guide/deployment.html b/snapshot/guide/deployment.html
index 8b8cb35a554..0e4a2086f42 100644
--- a/snapshot/guide/deployment.html
+++ b/snapshot/guide/deployment.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 21 Deployment 4.0.13
+ 21 Deployment 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -135,7 +135,7 @@
21 Deployment
- Version: 4.0.13
+ Version: 5.0.1
@@ -159,7 +159,7 @@ Table of Contents
21 Deployment
-
@@ -173,7 +173,7 @@ 21 Deployment
21.1 Standalone
-
@@ -250,7 +250,7 @@ A TAR/ZIP distribution
21.2 Container Deployment (e.g. Tomcat)
-
@@ -297,7 +297,7 @@ Application servers
21.3 Deployment Configuration Tasks
-
@@ -341,10 +341,13 @@ Settin
diff --git a/snapshot/guide/gettingStarted.html b/snapshot/guide/gettingStarted.html
index e50b744c209..50a1febd656 100644
--- a/snapshot/guide/gettingStarted.html
+++ b/snapshot/guide/gettingStarted.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 2 Getting Started 4.0.13
+ 2 Getting Started 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -128,14 +128,14 @@
(Quick Reference)
-
+
2 Getting Started
- Version: 4.0.13
+ Version: 5.0.1
@@ -189,7 +189,7 @@ Table of Contents
2 Getting Started
-
@@ -201,20 +201,20 @@ 2 Getting Started
2.1 Installation Requirements
-
-Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
+Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
-On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
@@ -239,7 +239,7 @@ 2.1 Installation Requirements
2.2 Downloading and Installing
-
@@ -271,7 +271,7 @@ Install with SDKMAN
-sdk install grails 4.0.13
+sdk install grails 5.0.1
@@ -307,12 +307,20 @@ Unix/Linux
-
-===Windows
-** Copy the path to the bin directory inside the grails folder you have downloaded, for example,
----
-C:/path_to_grails/bin
----
+
+
+Windows
+
+
+-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
+
+
+
+C:/path_to_grails/bin
+
@@ -321,11 +329,11 @@ Unix/Linux
-
-
-Start + R
+
+
+Start + R
+
-
-
@@ -341,7 +349,7 @@
Unix/Linux
-Grails version: 4.0.13
+Grails version: 5.0.1
@@ -352,7 +360,7 @@ Unix/Linux
2.3 Creating an Application
-
@@ -387,7 +395,7 @@ 2.3 Creating an Application
2.4 A Hello World Example
-
@@ -517,7 +525,7 @@ 2.4 A Hello World Example
2.5 Using Interactive Mode
-
@@ -539,7 +547,7 @@ 2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
-
@@ -548,7 +556,7 @@ 2.6 Getting Set Up in an IDE
IntelliJ IDEA
-IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@ IntelliJ IDEA
Spring Value Annotation
You can use Spring’s Value annotation to inject configuration values:
+You can use Spring’s Value annotation to inject configuration values:
Spring Value Annotation
4.1.1 Options for the YML format Config
Using system properties
External configuration
Grails will read application.(properties|yml) from the ./config or the current directory by default.
-As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.1.x/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
+As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.5.2/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
Grails will read application.(properties|yml) from the ./config or the current directory by default.
-As Grails is a SpringBoot configuration options are available as well, for documentation please consult: https://docs.spring.io/spring-boot/docs/2.1.x/reference/html/boot-features-external-config.html#boot-features-external-config-application-property-files
External configuration
4.1.2 Built in options
Runtime settings
grails.mime.types - A map of supported mime types used for Content Negotiation.
grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
grails.serverURL - A string specifying the server URL portion of absolute links, including server name e.g. grails.serverURL="http://my.yourportal.com". See createLink. Also used by redirects.
grails.views.gsp.sitemesh.preprocess - Determines whether SiteMesh preprocessing happens. Disabling this slows down page rendering, but if you need SiteMesh to parse the generated HTML from a GSP view then disabling it is the right option. Don’t worry if you don’t understand this advanced property: leave it set to true.
Runtime settings
4.1.3 Logging
Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.groovy file.
| - - | -
-If you prefer XML you can replace the logback.groovy file with a logback.xml file instead.
- |
-
Since Grails 3.0, logging is handled by the Logback logging framework and can be configured with the grails-app/conf/logback.xml file.
For more information on configuring logging refer to the Logback documentation on the subject.
+For more information on configuring logging refer to the Logback documentation on the subject.
4.1.3.1 Logger Names
4.1.3.1 Logger Names
4.1.3.2 Masking Request Parameters From Stacktrace Logs
4.1.3.2 Masking Request Para
4.1.3.3 External Configuration File
-
@@ -751,21 +739,21 @@ 4.1.3.3 External Configuration File
grails-app/conf/application.yml
logging:
- config: /Users/me/config/logback.groovy
+ config: /Users/me/config/logback.xml
logging:
- config: /Users/me/config/logback.groovyAlternatively, you can supply the configuration file location with a system property:
$ ./gradlew -Dlogging.config=/Users/me/config/logback.groovy bootRun
$ ./gradlew -Dlogging.config=/Users/me/config/logback.xml bootRun
Or, you could use an environment variable:
$ export LOGGING_CONFIG=/Users/me/config/logback.groovy
+$ export LOGGING_CONFIG=/Users/me/config/logback.xml
$ ./gradlew bootRun
4.1.3.3 External Configuration File
4.1.4 GORM
4.1.4 GORM
4.1.5 Configuring an HTTP proxy
4.1.5 Configuring an HTTP proxy
4.2 The Application Class
4.2 The Application Class
Every new Grails application features an Application class within the grails-app/init directory.
The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
The Application class subclasses the GrailsAutoConfiguration class and features a static void main method, meaning it can be run as a regular application.
Registering Additional Beans
The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
The Application class can also be used as a source for Spring bean definitions, simply define a method annotated with the Bean and the returned object will become a Spring bean. The name of the method is used as the bean name:
Registering Additional Beans
4.2.3 The Application LifeCycle
The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
The Application class also implements the GrailsApplicationLifeCycle interface which all plugins implement.
This means that the Application class can be used to perform the same functions as a plugin. You can override the regular plugins hooks such as doWithSpring, doWithApplicationContext and so on by overriding the appropriate method:
4.2.3 The Application LifeCycle
4.3 Environments
Packaging and Running
Programmatic Environment Detection
-Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
+Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
@@ -1150,7 +1138,7 @@ Generic Per Environment Execution4.4 The DataSource
-
@@ -1393,7 +1381,7 @@ More on dbCreate
4.4.1 DataSources and Environments
-
@@ -1429,7 +1417,7 @@ 4.4.1 DataSources and Environments
4.4.2 Automatic Database Migration
-
@@ -1481,7 +1469,7 @@ 4.4.2 Automatic Database Migration
4.4.3 Transaction-aware DataSource Proxy
-
@@ -1498,7 +1486,7 @@ 4.4.3 Transaction-aware DataSource Prox
4.4.4 Database Console
-
@@ -1508,14 +1496,14 @@ 4.4.4 Database Console
The H2 database console is a convenient feature of H2 that provides a web-based interface to any database that you have a JDBC driver for, and it’s very useful to view the database you’re developing against. It’s especially useful when running against an in-memory database.
-You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
+You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
4.4.5 Multiple Datasources
-
@@ -1819,7 +1807,7 @@ Transactions across multiple
The BE1PC implementation was added in Grails 2.3.6. . Before this change additional datasources didn’t take part in transactions initiated in Grails. The transactions in additional datasources were basically in auto commit mode. In some cases this might be the wanted behavior. One reason might be performance: on the start of each new transaction, the BE1PC transaction manager creates a new transaction to each datasource. It’s possible to leave an additional datasource out of the BE1PC transaction manager by setting transactional = false in the respective configuration block of the additional dataSource. Datasources with readOnly = true will also be left out of the chained transaction manager (since 2.3.7).
-By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
+By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
You can exclude transaction manager beans from the BE1PC implementation with this configuration option:
@@ -1843,7 +1831,7 @@ XA and Two-phase Commit
When the Best Efforts 1PC pattern isn’t suitable for handling transactions across multiple transactional resources (not only datasources), there are several options available for adding XA/2PC support to Grails applications.
-The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
+The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
@@ -1851,7 +1839,7 @@ XA and Two-phase Commit
4.5 Versioning
-
@@ -1860,7 +1848,7 @@ 4.5 Versioning
Detecting Versions at Runtime
-You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
+You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
@@ -1891,7 +1879,7 @@ Detecting Versions at Runtime
4.6 Dependency Resolution
-
@@ -1904,7 +1892,7 @@ 4.6 Dependency Resolution
-
+
diff --git a/snapshot/guide/contributing.html b/snapshot/guide/contributing.html
index 7f16a4feebe..cd5674d6586 100644
--- a/snapshot/guide/contributing.html
+++ b/snapshot/guide/contributing.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 22 Contributing to Grails 4.0.13
+ 22 Contributing to Grails 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -133,7 +133,7 @@
22 Contributing to Grails
- Version: 4.0.13
+ Version: 5.0.1
@@ -160,7 +160,7 @@ Table of Contents
22 Contributing to Grails
-
@@ -174,7 +174,7 @@ 22 Contributing to Grails
22.1 Report Issues in Github's issue tracker
-
@@ -203,7 +203,7 @@ Reviewing issues
22.2 Build From Source and Run Tests
-
@@ -378,7 +378,7 @@ Debugging Grails or a Grails
22.3 Submit Patches to Grails Core
-
@@ -497,7 +497,7 @@ Say what your pull request is for22.4 Submit Patches to Grails Documentation
-
diff --git a/snapshot/guide/deployment.html b/snapshot/guide/deployment.html
index 8b8cb35a554..0e4a2086f42 100644
--- a/snapshot/guide/deployment.html
+++ b/snapshot/guide/deployment.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 21 Deployment 4.0.13
+ 21 Deployment 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -135,7 +135,7 @@
21 Deployment
- Version: 4.0.13
+ Version: 5.0.1
@@ -159,7 +159,7 @@ Table of Contents
21 Deployment
-
@@ -173,7 +173,7 @@ 21 Deployment
21.1 Standalone
-
@@ -250,7 +250,7 @@ A TAR/ZIP distribution
21.2 Container Deployment (e.g. Tomcat)
-
@@ -297,7 +297,7 @@ Application servers
21.3 Deployment Configuration Tasks
-
@@ -341,10 +341,13 @@ Settin
diff --git a/snapshot/guide/gettingStarted.html b/snapshot/guide/gettingStarted.html
index e50b744c209..50a1febd656 100644
--- a/snapshot/guide/gettingStarted.html
+++ b/snapshot/guide/gettingStarted.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 2 Getting Started 4.0.13
+ 2 Getting Started 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -128,14 +128,14 @@
(Quick Reference)
-
+
2 Getting Started
- Version: 4.0.13
+ Version: 5.0.1
@@ -189,7 +189,7 @@ Table of Contents
2 Getting Started
-
@@ -201,20 +201,20 @@ 2 Getting Started
2.1 Installation Requirements
-
-Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
+Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
-On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
@@ -239,7 +239,7 @@ 2.1 Installation Requirements
2.2 Downloading and Installing
-
@@ -271,7 +271,7 @@ Install with SDKMAN
-sdk install grails 4.0.13
+sdk install grails 5.0.1
@@ -307,12 +307,20 @@ Unix/Linux
-
-===Windows
-** Copy the path to the bin directory inside the grails folder you have downloaded, for example,
----
-C:/path_to_grails/bin
----
+
+
+Windows
+
+
+-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
+
+
+
+C:/path_to_grails/bin
+
@@ -321,11 +329,11 @@ Unix/Linux
-
-
-Start + R
+
+
+Start + R
+
-
-
@@ -341,7 +349,7 @@
Unix/Linux
-Grails version: 4.0.13
+Grails version: 5.0.1
@@ -352,7 +360,7 @@ Unix/Linux
2.3 Creating an Application
-
@@ -387,7 +395,7 @@ 2.3 Creating an Application
2.4 A Hello World Example
-
@@ -517,7 +525,7 @@ 2.4 A Hello World Example
2.5 Using Interactive Mode
-
@@ -539,7 +547,7 @@ 2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
-
@@ -548,7 +556,7 @@ 2.6 Getting Set Up in an IDE
IntelliJ IDEA
-IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@ IntelliJ IDEA
Programmatic Environment Detection
Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
+Within your code, such as in a Gant script or a bootstrap class you can detect the environment using the Environment class:
Generic Per Environment Execution4.4 The DataSource
-
@@ -1393,7 +1381,7 @@ More on dbCreate
4.4.1 DataSources and Environments
-
@@ -1429,7 +1417,7 @@ 4.4.1 DataSources and Environments
4.4.2 Automatic Database Migration
-
@@ -1481,7 +1469,7 @@ 4.4.2 Automatic Database Migration
4.4.3 Transaction-aware DataSource Proxy
-
@@ -1498,7 +1486,7 @@ 4.4.3 Transaction-aware DataSource Prox
4.4.4 Database Console
-
@@ -1508,14 +1496,14 @@ 4.4.4 Database Console
4.4.4 Database Console
4.4.4 Database Console
The H2 database console is a convenient feature of H2 that provides a web-based interface to any database that you have a JDBC driver for, and it’s very useful to view the database you’re developing against. It’s especially useful when running against an in-memory database.
You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
+You can access the console by navigating to http://localhost:8080/h2-console in a browser. See the Spring Boot H2 Console Documentation for more information on the options available.
4.4.5 Multiple Datasources
Transactions across multiple
The BE1PC implementation was added in Grails 2.3.6. . Before this change additional datasources didn’t take part in transactions initiated in Grails. The transactions in additional datasources were basically in auto commit mode. In some cases this might be the wanted behavior. One reason might be performance: on the start of each new transaction, the BE1PC transaction manager creates a new transaction to each datasource. It’s possible to leave an additional datasource out of the BE1PC transaction manager by setting transactional = false in the respective configuration block of the additional dataSource. Datasources with readOnly = true will also be left out of the chained transaction manager (since 2.3.7).
By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
By default, the BE1PC implementation will add all beans implementing the Spring PlatformTransactionManager interface to the chained BE1PC transaction manager. For example, a possible JMSTransactionManager bean in the Grails application context would be added to the Grails BE1PC transaction manager’s chain of transaction managers.
You can exclude transaction manager beans from the BE1PC implementation with this configuration option:
@@ -1843,7 +1831,7 @@XA and Two-phase Commit
When the Best Efforts 1PC pattern isn’t suitable for handling transactions across multiple transactional resources (not only datasources), there are several options available for adding XA/2PC support to Grails applications.
The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
The Spring transactions documentation contains information about integrating the JTA/XA transaction manager of different application servers. In this case, you can configure a bean with the name transactionManager manually in resources.groovy or resources.xml file.
Detecting Versions at Runtime
You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
+You can detect the application version using Grails' support for application metadata using the GrailsApplication class. For example within controllers there is an implicit grailsApplication variable that can be used:
Detecting Versions at Runtime
4.6 Dependency Resolution
4.6 Dependency Resolution
- + diff --git a/snapshot/guide/contributing.html b/snapshot/guide/contributing.html index 7f16a4feebe..cd5674d6586 100644 --- a/snapshot/guide/contributing.html +++ b/snapshot/guide/contributing.html @@ -11,7 +11,7 @@ gtag('config', 'UA-82213539-2'); -22 Contributing to Grails
-Version: 4.0.13
+Version: 5.0.1
Table of Contents
22 Contributing to Grails
22 Contributing to Grails
22.1 Report Issues in Github's issue tracker
Reviewing issues
22.2 Build From Source and Run Tests
Debugging Grails or a Grails
22.3 Submit Patches to Grails Core
-
@@ -497,7 +497,7 @@ Say what your pull request is for22.4 Submit Patches to Grails Documentation
-
diff --git a/snapshot/guide/deployment.html b/snapshot/guide/deployment.html
index 8b8cb35a554..0e4a2086f42 100644
--- a/snapshot/guide/deployment.html
+++ b/snapshot/guide/deployment.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 21 Deployment 4.0.13
+ 21 Deployment 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -135,7 +135,7 @@
21 Deployment
- Version: 4.0.13
+ Version: 5.0.1
@@ -159,7 +159,7 @@ Table of Contents
21 Deployment
-
@@ -173,7 +173,7 @@ 21 Deployment
21.1 Standalone
-
@@ -250,7 +250,7 @@ A TAR/ZIP distribution
21.2 Container Deployment (e.g. Tomcat)
-
@@ -297,7 +297,7 @@ Application servers
21.3 Deployment Configuration Tasks
-
@@ -341,10 +341,13 @@ Settin
diff --git a/snapshot/guide/gettingStarted.html b/snapshot/guide/gettingStarted.html
index e50b744c209..50a1febd656 100644
--- a/snapshot/guide/gettingStarted.html
+++ b/snapshot/guide/gettingStarted.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 2 Getting Started 4.0.13
+ 2 Getting Started 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -128,14 +128,14 @@
(Quick Reference)
-
+
2 Getting Started
- Version: 4.0.13
+ Version: 5.0.1
@@ -189,7 +189,7 @@ Table of Contents
2 Getting Started
-
@@ -201,20 +201,20 @@ 2 Getting Started
2.1 Installation Requirements
-
-Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
+Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
-On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
@@ -239,7 +239,7 @@ 2.1 Installation Requirements
2.2 Downloading and Installing
-
@@ -271,7 +271,7 @@ Install with SDKMAN
-sdk install grails 4.0.13
+sdk install grails 5.0.1
@@ -307,12 +307,20 @@ Unix/Linux
-
-===Windows
-** Copy the path to the bin directory inside the grails folder you have downloaded, for example,
----
-C:/path_to_grails/bin
----
+
+
+Windows
+
+
+-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
+
+
+
+C:/path_to_grails/bin
+
@@ -321,11 +329,11 @@ Unix/Linux
-
-
-Start + R
+
+
+Start + R
+
-
-
@@ -341,7 +349,7 @@
Unix/Linux
-Grails version: 4.0.13
+Grails version: 5.0.1
@@ -352,7 +360,7 @@ Unix/Linux
2.3 Creating an Application
-
@@ -387,7 +395,7 @@ 2.3 Creating an Application
2.4 A Hello World Example
-
@@ -517,7 +525,7 @@ 2.4 A Hello World Example
2.5 Using Interactive Mode
-
@@ -539,7 +547,7 @@ 2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
-
@@ -548,7 +556,7 @@ 2.6 Getting Set Up in an IDE
IntelliJ IDEA
-IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@ IntelliJ IDEA
21 Deployment
-Version: 4.0.13
+Version: 5.0.1
Table of Contents
21 Deployment
21 Deployment
21.1 Standalone
A TAR/ZIP distribution
21.2 Container Deployment (e.g. Tomcat)
Application servers
21.3 Deployment Configuration Tasks
Settin
diff --git a/snapshot/guide/gettingStarted.html b/snapshot/guide/gettingStarted.html
index e50b744c209..50a1febd656 100644
--- a/snapshot/guide/gettingStarted.html
+++ b/snapshot/guide/gettingStarted.html
@@ -11,7 +11,7 @@
gtag('config', 'UA-82213539-2');
- 2 Getting Started 4.0.13
+ 2 Getting Started 5.0.1
@@ -44,7 +44,7 @@
- 3Upgrading from Grails 3.3.x
+
4Configuration
@@ -128,14 +128,14 @@
(Quick Reference)
-
+
2 Getting Started
- Version: 4.0.13
+ Version: 5.0.1
@@ -189,7 +189,7 @@ Table of Contents
2 Getting Started
-
@@ -201,20 +201,20 @@ 2 Getting Started
2.1 Installation Requirements
-
-Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
+Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
-On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
@@ -239,7 +239,7 @@ 2.1 Installation Requirements
2.2 Downloading and Installing
-
@@ -271,7 +271,7 @@ Install with SDKMAN
-sdk install grails 4.0.13
+sdk install grails 5.0.1
@@ -307,12 +307,20 @@ Unix/Linux
-
-===Windows
-** Copy the path to the bin directory inside the grails folder you have downloaded, for example,
----
-C:/path_to_grails/bin
----
+
+
+Windows
+
+
+-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
+
+
+
+C:/path_to_grails/bin
+
@@ -321,11 +329,11 @@ Unix/Linux
-
-
-Start + R
+
+
+Start + R
+
-
-
@@ -341,7 +349,7 @@
Unix/Linux
-Grails version: 4.0.13
+Grails version: 5.0.1
@@ -352,7 +360,7 @@ Unix/Linux
2.3 Creating an Application
-
@@ -387,7 +395,7 @@ 2.3 Creating an Application
2.4 A Hello World Example
-
@@ -517,7 +525,7 @@ 2.4 A Hello World Example
2.5 Using Interactive Mode
-
@@ -539,7 +547,7 @@ 2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
-
@@ -548,7 +556,7 @@ 2.6 Getting Set Up in an IDE
IntelliJ IDEA
-IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@ IntelliJ IDEA
2 Getting Started
-Version: 4.0.13
+Version: 5.0.1
Table of Contents
2 Getting Started
2 Getting Started
2.1 Installation Requirements
Before installing Grails 4.0.13 you will need as a minimum a Java Development Kit (JDK) installed version 1.8 or above. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
Before installing Grails 5.0.1 you will need as a minimum a Java Development Kit (JDK) installed version 1.8. The most recent supported version of the JDK is 11. Download the appropriate JDK for your operating system, run the installer, and then set up an environment variable called JAVA_HOME pointing to the location of this installation.
To automate the installation of Grails we recommend SDKMAN which greatly simplifies installing and managing multiple Grails versions.
On some platforms (for example OS X) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
+On some platforms (for example macOS) the Java installation is automatically detected. However in many cases you will want to manually configure the location of Java. For example, if you’re using bash or another variant of the Bourne Shell:
2.1 Installation Requirements
2.2 Downloading and Installing
Install with SDKMAN
sdk install grails 4.0.13sdk install grails 5.0.1Unix/Linux
===Windows -** Copy the path to the bin directory inside the grails folder you have downloaded, for example, ---- -C:/path_to_grails/bin ----
+Windows
+-
+
-
+
Copy the path to the bin directory inside the grails folder you have downloaded, for example,
+
+
C:/path_to_grails/bin+
-
@@ -321,11 +329,11 @@
Unix/Linux
-
Start + R
+Start + R+
-
@@ -341,7 +349,7 @@
Unix/Linux
Grails version: 4.0.13Grails version: 5.0.1Unix/Linux
2.3 Creating an Application
2.3 Creating an Application
2.4 A Hello World Example
2.4 A Hello World Example
2.5 Using Interactive Mode
2.5 Using Interactive Mode
2.6 Getting Set Up in an IDE
2.6 Getting Set Up in an IDE
IntelliJ IDEA
IntelliJ IDEA is an excellent IDE for Grails 4.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
+IntelliJ IDEA is an excellent IDE for Grails 5.0 development. It comes in 2 editions, the free community edition and the paid-for ultimate edition.
The community edition can be used for most things, although GSP syntax higlighting is only part of the ultimate edition
@@ -566,7 +574,7 @@