Hey Yes, it's a bug: http://issues.gradle.org/browse/GRADLE-1442
In your case the workaround is to produce a different artifact. It is more natural approach anyway IMHO. Cheers! Szczepan On Mon, Jul 11, 2011 at 10:31 PM, Merlyn Albery-Speyer <[email protected]> wrote: > Hmm. > > All: Is this a known bug? > > On Jul 11, 2011 12:37 PM, "Adrian Abraham" <[email protected]> wrote: >> Merlyn, >> >> I've changed the dependencies block to: >> >>> dependencies { >>> compile group: 'foo', name: 'foo', version: '1.0-SNAPSHOT' >>> testCompile group: 'foo', name: 'foo', version: '1.0-SNAPSHOT' >>> testCompile group: 'foo', name: 'foo', version: '1.0-SNAPSHOT', >>> classifier: 'tests' >>> testCompile group: 'junit', name: 'junit', version: '4.8.2' >>> } >>> >> >> I'm getting the exact same behavior as before. Whichever dependency comes >> second is the one which is put on the classpath. >> >> - Adrian >> >> On Mon, Jul 11, 2011 at 2:57 PM, Merlyn Albery-Speyer < >> [email protected]> wrote: >> >>> Hi Adrian, when you use dependencies with classifiers you need to use the >>> more verbose form that and provide the classifier like so: >>> >>> .... classifier: "test" >>> On Jul 11, 2011 11:51 AM, "Adrian Abraham" <[email protected]> >>> wrote: >>> > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
