Adam Murdoch-3 wrote: > > > It looks like declaring the same module more than once, like you do above, > is broken. It was never very well defined, and so it a bit of a > coincidence that what you tried actually worked. I've added a JIRA issue > for this: http://jira.codehaus.org/browse/GRADLE-1143 > > You could probably achieve what you need by simply getting rid of the > modules altogether: > > compile(':rio:4.0') { > artifact { ... } > } > > testCompile(':rio:4.0') { > artifact { ... } > } > > Now, that I am rereading this thread I realize, that artifacts of a SW package not the same as its dependencies. Defining the same module again with a different set of artifacts does not make much sense.
So if I get it right my options are to use: 1. whole client module dependency definition (containing each artifact): which then does not show what artifacts are exactly used in different build phases (like compile vs testRuntime here) 2. "plain" dependency definition: which shows what artifact used at what build phase, but does not show transitive dependencies Can we have somehow all the goodies? This exemplifies how much one expect from gradle seeing its capabilities ;-) Thanks! -- View this message in context: http://gradle.1045684.n5.nabble.com/0-9-rc1-regression-in-ant-task-tp2796760p2804915.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
