In fact, there's an example of the use of dependency configurations in http://www.gradle.org/dependency_management.html
(although seemingly not in the user guide, for some reason). Search for "Dependency configurations" and have a look at Example 196... ap > >From: John Murph <[email protected]> >To: [email protected] >Sent: Fri, 19 November, 2010 20:54:24 >Subject: Re: [gradle-user] Depending on one jar of a multi-jar project > >If you have source sets for these jars, here is what we do: > >dependencies.project(path: <module>, configuration: <sourceset>) > >So, if moduleA produces a-extra.jar using a sourceset named extra, then >moduleB >can depend on that jar using > >dependencies.project(path: moduleA, configuration: 'extra') > >This is not clear at all, and I think I only found it by digging through >source >code, and it might not work in all cases (like uploading to a Maven repo), but >for us it works for getting the dependencies set right. > > > >On Thu, Nov 18, 2010 at 6:12 PM, Andrew Spina <[email protected]> wrote: > >Hi All, >> >>I have a project that generates multiple jars (one using Javacc and one using >>Jaxb). I have other projects in the same build that want to depend on only >>one >>or the other of these jars. How do I refer to just one jar in my build file? >>I'm >>guessing it has to do with the configurations that the Jars are assigned to. >>I've looked through the documentation and asked Google. I haven't found an >>answer. >> >>This is my first post to the list, but I've worked with both Ant and Maven. >>Gradle is a great alternative. Thanks for putting it together. >> >>Cheers, >> >>Andy >> >> -- >John Murph >Automated Logic Research Team >
