Our project Gradle support code to mangle standard Eclipse files, based on an older version of Gradle. Being on a older version of Gradle and now upgrading to the newest Gradle it is great to see all the new configuration capabilities. What I am trying to understand is where to hook into Eclipse generation to create files for Eclipse plugins that aren't supported by Gradle or a Gradle plugin yet.
Before I was using a doLast on the eclipse task but, that doesn't work anymore in version 1.0.7. I moved all these to an eclipseClasspath.doLast. I wasn't crazy about this because my files really don't have anything to do with the classpath setup in Eclipse. Any thoughts on a better approach? I would like a place that would hook in right after Gradle is done with the entire Eclipse generation build phase. What is the intended best practices? I know plugins is one way but, I am looking for an approach for teams that doesn't necessarily require building a plugin. For me that was a big plus over Maven and I really hope that will continue to be true with Gradle. Thanks, Jas
