grails-3.1

问题 From Grails 3.1.9 relase notes: Integration Test Port Integration and functional tests now run on a random port instead of the same port as the application by default. This is to avoid port conflict problems when the application is already running. Integration tests that hard code the port will need to be altered to use the serverPort property of tests marked with @Integration I was normally getting the integration test url with import grails.util.Holders ... .. . def

问题 From Grails 3.1.9 relase notes: Integration Test Port Integration and functional tests now run on a random port instead of the same port as the application by default. This is to avoid port conflict problems when the application is already running. Integration tests that hard code the port will need to be altered to use the serverPort property of tests marked with @Integration I was normally getting the integration test url with import grails.util.Holders ... .. . def

问题 From Grails 3.1.9 relase notes: Integration Test Port Integration and functional tests now run on a random port instead of the same port as the application by default. This is to avoid port conflict problems when the application is already running. Integration tests that hard code the port will need to be altered to use the serverPort property of tests marked with @Integration I was normally getting the integration test url with import grails.util.Holders ... .. . def

问题 I am tring to get a jar dependency from Maven via the grails 3.1.5 gradle dependency Resolution . How do I increase timeout that gradle takes to get a maven dependency. Sure I have seen that the dependency takes quiet a longer time to be downloaded. But how can I configure gradle to wait longer in order to download the dependency 回答1: The feature was added in Gradle here: https://github.com/gradle/gradle/pull/3041 You can increase the timeout with 2 properties: ./gradlew build -Dhttp

问题 I am tring to get a jar dependency from Maven via the grails 3.1.5 gradle dependency Resolution . How do I increase timeout that gradle takes to get a maven dependency. Sure I have seen that the dependency takes quiet a longer time to be downloaded. But how can I configure gradle to wait longer in order to download the dependency 回答1: The feature was added in Gradle here: https://github.com/gradle/gradle/pull/3041 You can increase the timeout with 2 properties: ./gradlew build -Dhttp

问题 App Info: Grails Version: 3.1.8 Groovy Version: 2.4.6 JVM Version: 1.8.0_60 I'm running grails package to get runnable archives however I come across the following error: Could not resolve all dependencies for configuration ':gspCompile'. Could not resolve javax.servlet:javax.servlet-api:3.1.0. Required by: app:app:0.1 Could not resolve javax.servlet:javax.servlet-api:3.1.0. Could not get resource 'https://repo.grails.org/grails/core/javax/servlet/javax.servlet-api/3.1.0/javax.servlet-api-3.1

问题 We would like to use Log4j2 as the log binding with grails 3. From what I can figure out so far. We have many subordinate dependencies that use a variety of loggers, so we need to use the SLF4J API. Then, instead of letting grails / groovy / spring re-direct the SLF4J API to the Logback binding, we need to re-direct each to the Log4j2 binding. Since grails 3 uses the Logback binding, I am planning to go through each dependency in the build.gradle, exclude the Logback binding, and include the

问题 We would like to use Log4j2 as the log binding with grails 3. From what I can figure out so far. We have many subordinate dependencies that use a variety of loggers, so we need to use the SLF4J API. Then, instead of letting grails / groovy / spring re-direct the SLF4J API to the Logback binding, we need to re-direct each to the Log4j2 binding. Since grails 3 uses the Logback binding, I am planning to go through each dependency in the build.gradle, exclude the Logback binding, and include the

问题 How do I make Grails 3.1.1 user Hibernate 5? The following actions report Hibernate version 4.3.11.Final: In Grails 3.1.1 grails create-app hello311 edit BootStrap.groovy as shown below grails run-app Console shows: Hibernate version is: 4.3.11.Final class BootStrap { def init = { servletContext -> println "Hibernate version is: ${org.hibernate.Version.getVersionString()}" } def destroy = {} } My build.gradle is unedited. The create-app command resulted in the following build.gradle file:

问题 I have a domain class which extends another groovy class with same name but in different package in a different library. The problem is when I modify instances on the domain class, it is not marked as dirty & hence changes are not persisted. I have read that grails 3 release has some enhancements to dirty checking & this could be a bug or I am missing something. New objects are saved properly without any issues, I have used isDirty() method on modified domain object as well as modified