One thing that strikes me is that processResources {} shouldn't be nested
inside war {}. These are two separate tasks.-- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw Neil Chaudhuri wrote: > > I have a web application that I am building with Milestone 3, and I have > the following closure: > > war { > baseName = webContext > processResources { > inputs.file new File("../gradle.properties") > logger.info "baseUrl: " + baseUrl > filter ReplaceTokens, tokens: [ > timestamp: timestamp, > projectVersion: project.version, > baseUrl: baseUrl > ] > } > } > > When I run the war task (the default for my build), I find that the > filtering never happens, so variables like @baseUrl@ in my configuration > files never get interpolated. These files are in src/main/resources at > arbitrary depth. > > Any insight into what might be causing this is appreciated. > > Thanks. > -- View this message in context: http://gradle.1045684.n5.nabble.com/File-Filtering-Not-Happening-tp4843308p4843877.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
