I am porting a large Ivy-based build system to Gradle and I am trying to figure out what to do about configurations. I had pretty much stuck with the Ivy defaults for our hundreds of projects and now tens of thousands of published modules. And now looking at Gradle, and especially the Java plugin, I see that these are different and I'm not sure whether I should migrate to Gradle's or extend/modify Gradle to work with mine.
Here are the ones I question: Ivy's 'master' seems to match Gradles 'archives'. Master seems more general, but this is a simple one-one name change mapping I guess, so maybe I could live with it. Gradle is missing Ivy's 'provided'. This wouldn't be possible to do without. Are there any plans to add this to the standard set for the Java plugin? How much trouble will I get myself into if I start poking this in all over. Ivy's 'test' has been split up into 'testCompile' and 'testRuntime' in Gradle. I think this makes more sense, so I'll migrate. I guess anything that was using test would just map to testCompile and get inherited by testRuntime? Any other Ivy to Gradle migrators? What have you done in this area? -- View this message in context: http://gradle.1045684.n5.nabble.com/Ivy-vs-Gradle-configurations-tp4544242p4544242.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
