And if I have a pre-existing filters.xml, just a matter of parsing it and building up the filter map?
I guess I wasn't as clear as I should be.. just trying to find as many "awesome" ways to bridge the gap between ant/maven. I'm trying to get my workplace to adopt gradle hah, and the maven people are one set of arguements.. and an "Ant person" came at me about their many-many page filters.xml file. Custom groovy code to process it with XmlSlurper is "super-cool" but isn't as Gradley (groovy) as I figured it might be. Roger On Dec 22, 2009, at 10:57 AM, Steve Appling wrote: > > > On 12/22/2009 8:39 AM, Roger Studner wrote: >> Was curious.. I found some chatter about this around Gradle 0.4 on various >> sites.. but I can't seem to find an example that works with 0.8. >> >> I have an ant build i'm converting over, that makes use of a filters.xml >> (@OPTION_CACHING_TRUE@ kind of nonsense). >> >> Can I 'hook that in' in a gradle way to handle it? or do I need to do some >> kind of ant.copy adhoc thing that just copy a file from an out of bounds >> location into the right spot "pre" everything else? >> >> Thanks! >> Roger >> > > You could replace the processResources task with a Copy task to copy to the > classes directory and use filtering. See the top of the Copy task javadoc > (http://gradle.org/0.8/docs/javadoc/?org/gradle/api/tasks/Copy.html) for an > example of copying using filtering. > > -- > Steve Appling > Automated Logic Research Team > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
