I'd start out by implementing this as an ad-hoc task in the build script. Once you've got this working, you can think about moving the code into a script plugin in gradle/ or a task class in buildSrc/.
Not sure if that's the answer you've been looking for. Hope it helps. -- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw KlausUnger wrote > > Hi everybody, > > I'm running a mid-size Java - SpringMVC - Tiles project and recognized a > little problem while refactor-renaming pages. > > The pages are references from the Controllers with String literals, which > have to map some declarations in the various tiles/views config files. As > there is no good Tiles Support in STS or IDEA, those declarations and the > usage get broken. So, from time to time my view references in the code > point nowhere ... :( > > I just thought what would be the best solution to generate a java > class/enum with Constants for those literals before compiling the source > ... which would cause compilation errors, when some refactorings break the > view references. > > I'd prefere to go more the declarative gradle way (maybe write a custom > plugin) than writing some groovy logic in my build > > As I'm fairly new to groovy and gradle ... any ideas, hints, samples would > be highly appreciated! > > Thanks for your help in advance > K:) > -- View this message in context: http://gradle.1045684.n5.nabble.com/Best-solution-for-generating-Java-Constants-for-a-Tiles-Project-tp5086678p5087524.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
