--
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-disc...@googlegroups.com.
To post to this group, send email to grails-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grails-dev-discuss/562a11e5-6761-4c37-9052-58eb23b66721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
That is correct yes
To answer my own question, I think maybe:--src/main/resourcessrc/test/resourcesSeem to be the 'gradle way' of adding things to the classpath. I moved my TestDataConfig.groovy there for build-test-data and it seemed to work. Still validating if that's a good spot for .properties files and the like.-Aaron
On Thursday, October 22, 2015 at 3:13:26 PM UTC-4, Aaron wrote:Upgrading to Grails 3.0.9 and wasn't sure where non-compiled items that need to be accessible via the classpath. I know the grails-app/conf directory isn't compiled anymore. Previously one trick was to put .groovy or .properties files in the src/java path as those items were just copied directly into the classes/ directory.Is there a better place in Grails 3/Gradle world? Somewhere meant for that type of thing?Thanks,Aaron
You received this message because you are subscribed to the Google Groups "Grails Dev Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grails-dev-discuss+unsub...@googlegroups.com.