All: My project requires rmic compilation after compilation. This was fairly straightforward to add by creating a new rmic method and adding that method via doLast to the compile and testCompile tasks.
The one thing that was rather awkward was getting the classpath used by the compile and testCompile tasks respectively. After going through the source I ended up with the following call: List classpath = GUtil.addLists(<task>.classpathConverter.createFileClasspath(project.rootDir, <task>.unmanagedClasspath),compile.dependencyManager.resolveTask(<task>.name) ) Is there a simpler call? If not, is there a technical reason why not? It seems to me that grabbing the classpath is likely to be a common need and should be supported by a simple call => compile.getClasspath() I'll be glad to add a Jira item if this sounds like a reasonable idea. I'd offer to provide a patch, but I'm not sure I'm familiar enough with the architecture/implementation yet to do it right. If someone would point me in the right direction, I will be glad to come up with a patch. Thx! -steve Stephen Nesbitt Absaroka Technical Consulting -- View this message in context: http://www.nabble.com/Getting-dervied-classpath-tp19959927p19959927.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
