The reason “Config.class” is appearing in your jar is because you specified “Config.groovy” in the src/main/resources. The compiler sees the “.groovy” suffix and compiles the file into a “.class” flie. Simply changing the filename to something like “Config.properties” should stop the name from changing work.
From: Guy Matz [mailto:[email protected]] Sent: Friday, April 15, 2016 1:02 PM To: [email protected] Subject: Re: ConfigSlurper not finding Config.groovy in jar As usual, the Groovy solution is far simpler than anticipated. Thank you!! On Fri, Apr 15, 2016 at 1:25 PM, John Wagenleitner <[email protected]<mailto:[email protected]>> wrote: If the build is compiling the file you probably either need to copy it into your jar from another location or you might be able to use the #parse(Class) method of ConfigSlurper. def config = new ConfigSlurper().parse(Config) On Fri, Apr 15, 2016 at 9:07 AM, Guy Matz <[email protected]<mailto:[email protected]>> wrote: Hi! I can't seem to find and slurp in a config file that's contained in a jar. I think part of the problem may be that the config.groovy file is being compiled into a class, but can't figure out the right way to go about slurping it in . . . from an ancient post I have the following code: def InputStream is = getClass().getResourceAsStream('/Config.groovy') def config = new ConfigSlurper().parse(is.getText()) The getClass()... return null. My directory structure is: src/main/resources/Config.groovy however my jar looks contains Config.class Anyone know what I'm doing wrong here? Thanks a lot! Guy
