Is resource filtering in Gradle possible without using tokens?

Question

The recommended way to do resource filtering in Gradle is by having tokens in the properties file and then replacing them when processing.

Example

# config.properties
hostname = @myhost@

and in build.gradle do something like below

processResources {
   filter ReplaceTokens, tokens: [
      "myhost": project.property('myhost')
   ]
}

The problem with this approach is that it won't work when running from IDEs like eclipse. I would like the property files to be free of Gradle specific tokens i.e just have

hostname = localhost

but have option to replace it when building from Gradle.

Answer 1

You could use the following (not tested):

processResources {
    filesMatching('**/config.properties') {
        filter {
            it.replace('localhost', project.property('myhost'))
        }
    }
}

Or you could have a default file, used during development in your IDE, and have another file containing tokens and replacing the development one when building using gradle. Something like this (not tested)

processResources {
    exclude '**/config.properties'
    filesMatching('**/config-prod.properties') {
        setName 'config.properties'
        filter ReplaceTokens, tokens: [
            "myhost": project.property('myhost')
        ]
    }
}

Answer 2

Can use thing like placeholder if you want.

In config.properties file

var1=${var1}
var2=${var2}

In gradle.properties file

processResources {
    filesMatching('**config.properties') {
        expand(
            'var1': project.property('var1'),
            'var2': project.property('var2'),
        )
    }
}

Answer 3

The spring-boot approach

project.version=X.X.X.X
[email protected]@

http://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#production-ready-application-info-automatic-expansion