Spencer McEwen

Created June 15, 2016 17:58

Thanks - I think this is working good enough for now. I can work around the environment name issue

1. Community
2. IntelliJ IDEA Users
3. Grails 3 not automatically hot swapping changed code after upgrading to 2016.1.3

• 0 votes

Created June 15, 2016 14:03

Thanks for your help troubleshooting this. I'm using Grails 3.1.4 with Java 1.8.0_92 from Oracle.  The only VM option in my Gradle debug launcher is to set the grails.env to local: -Dgrails.env=loc...

1. Community
2. IntelliJ IDEA Users
3. Grails 3 not automatically hot swapping changed code after upgrading to 2016.1.3

• 0 votes

Created June 14, 2016 18:49

I removed all the temporary build directories: build, .gradle, and out - then refreshed the Gradle project but I still have the same problem.

1. Community
2. IntelliJ IDEA Users
3. Grails 3 not automatically hot swapping changed code after upgrading to 2016.1.3

• 0 votes

Created June 14, 2016 18:36

I don't have a refresh task but I've done various combinations of clean and build without any change.  I noticed that if I change some code and do build -> make project I get this error:  

1. Community
2. IntelliJ IDEA Users
3. Grails 3 not automatically hot swapping changed code after upgrading to 2016.1.3

• 0 votes

Created June 14, 2016 18:21

1. Community
2. IntelliJ IDEA Users
3. Grails 3 not automatically hot swapping changed code after upgrading to 2016.1.3

• 0 votes