On 26/09/2011, at 7:40 PM, Carlton Brown wrote: > On Mon, Sep 26, 2011 at 2:31 PM, Luke Daley <[email protected]> wrote: > > > The “java” plugin wires the model together in such a way that the compile > classpath for the project ends up being the “compile” configuration (which is > like a collection of files). When the files are needed, e.g. at compile time, > Gradle will implicitly perform the resolve and make the files available to > the compiler. As far as the compile machinery is concerned, it's just > receiving a bunch of files and the resolution happens seamlessly. > > What if I need to do it explicitly? Say I have a configuration called > 'hammer' and a task also called 'hammer', how do I code it so that I have > hammer dependencies on hammer's classpath at hammer time?
You still wouldn't need to do it explicitly. What you would want is to “wire” the configuration to the property of the task that specifies the compile time classpath. Whether it's a configuration where the files come from a remote repository or is some other kind of collection of files is irrelevant. There is a key difference between Gradle and Ivy in that Gradle has a much richer model and things are less direct. This richer model enables Gradle to do a lot of work for you. So basically, you are trying to find out how to do “X” that you are used to doing with Ivy but the same concept does not transfer in this new world. > Also, I notice that Gradle does not accept a version string of > 'latest.integration' which in Ivy would signify the latest revision published > with a status of 'integration'. Is Gradle aware of Ivy statuses at all, or > does it have some analogous function? > > > What kind of repository/resolver are you using? > > HTTP (Artifactory). How do you declare the repository in your Gradle build? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
