thanks for you reply, that was helpful but I am stucked with the configurations now. They just do not resolve. However i gave up the idea at the moment as long as it is not directly supported by gradle and it doesn't create a big mess I can live with it for now. But the thing I am trying now is to do configurations inheritance and seems it's not very easy at the moment. I read some mailing list where gradle developers mentioned they will add some support through closure to the addDependency method in DefaultDependencyManager or provide a wrapper or something for an Ivy object. However, the post is one week ago and presumbaly this will not be available soon. My question is : is there any gradle way to do ivy configuration inheritance ? or should I go down to Ivy API ?
Thanks very much for your kind help Razvan mvlcek wrote: > > > Dragut Razvan wrote: >> >> >> However, gradle complains that there's no method signature >> addDependency(..... , .....) in DefaultDependencyManager. I had a look at >> the source and indeed there's no such method there. >> I've tried some other ways around with the "dependencies" object but I >> failed with those attempts as well. >> > > see > http://www.nabble.com/Dependency-to-a-module-configuration--to19990983.html > > Basically you can do it like this: > > DefaultDependencyDescriptor dd(String conf, String descr) { > String[] parts = descr.split(":"); > DefaultDependencyDescriptor dd = new DefaultDependencyDescriptor( > new ModuleRevisionId(new ModuleId(parts[0], parts[1]), > parts[2]), false, false) > return dd > } > > dependencies { > ... > dependencyDescriptors.add dd("compile", > "org.apache.cxf:cxf:2.0.6") > ... > > > -- View this message in context: http://www.nabble.com/Move-dependencies-to-separate-file-tp20363163p20372853.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
