On 26/09/2011, at 8:35 PM, Carlton Brown wrote:

> On Mon, Sep 26, 2011 at 2:50 PM, Luke Daley <[email protected]> wrote:
> 
> 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.
> 
> 
> I am just trying to see how jars in configuration X are assigned to the 
> classpath of task X, when X is not named 'compile'.   This would illustrate 
> for me how the wiring works, so that I know how to set up the right 
> conditions for indirect behavior for non-default inputs.   

Tasks in general don't have a classpath. Something like a compile task would 
though so I'll assume that's what you are talking about.

You can see the API for the Java compile task here: 
http://gradle.org/current/docs/javadoc/org/gradle/api/tasks/compile/Compile.html

Though, what you are interested in is the 
http://gradle.org/current/docs/javadoc/org/gradle/api/tasks/compile/AbstractCompile.html#setClasspath(org.gradle.api.file.FileCollection)
 method.

So you if all you want to do is wire a configuration to a compile task, you 
would do:

configurations {
        myCustomConfiguration // creates the configuration
}

dependencies {
        myCustomConfiguration "some-org:some-artifact:1.0"
}

task customCompile(type: Compile) {
        // other task configuration
        classpath = configurations.myCustomConfiguration
}

>  
> 
>> 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?
> 
> It looks like this (which could be totally wrong)
> 
>   ivy {
>     name= 'libs-trunk'
>     userName = 'ivyuser'
>     password = 'ivypass'
>     artifactPattern 
> 'http://my.server/aritfactory/libs-trunk/[organisation]/[module]/[revision]/[artifact]-[revision](-[classifier]).[ext]'
>   }


Unfortunately, you are hitting http://issues.gradle.org/browse/GRADLE-1789. 
This is high on the priority list for 1.0.

There is a workaround which is currently not listed on that ticket, but will be 
very soon.

-- 
Luke Daley
Principal Engineer, Gradleware 
http://gradleware.com

Reply via email to