Closed DPUkyle closed 8 years ago
As mentioned in the log for df5fb6c, I think we can manage this in configuration. Closing as won't fix
.
Reopening; turns out we actually need a closure for execution-time resolution of dependencies in the Guidewire build.
Fixed and appears to be working; will continue to monitor in Guidewire's test environment.
Just a thought - couldn't we also make the classpath
property a Closure too? Then we could set it dynamically at execution time and avoid the need to use orderedClasspath
Guidewire's build has a unique requirement to do depth-first traversal of the dependency tree.
Guidewire has a separate process to implement that logic, but the results of that process need to influence the build classpath (specifically, its ordering).
If the optional
orderClasspath
property is set, it should supercede/replace the normalclasspath
argument.