Thanks for the tip. I'll head that way with the code: what you're seeing is iterative development at work.
~~ Robert. On Tue, Apr 24, 2012 at 8:07 AM, Luke Daley <[email protected]> wrote: > > On 23/04/2012, at 10:43 AM, Robert Fischer wrote: > >> Looks like this is working: >> task ghUpload(dependsOn:[configurations.archives.allArtifacts]) { >> … >> } > > You should rewrite your upload task to accept a FileCollection parameter, and > annotate that parameter with @InputFiles. > > say… > > class GhUpload extends DefaultTask { > @InputFiles > FileCollection artifacts > > … > } > > then… > > task ghUpload(type: GhUpload) { > artifacts = configurations.archives.allArtifacts > } > > Gradle will then infer/manage the dependencies for you. > >> Is this a bug? I'd expect "configurations.archives" to be functionally >> equivalent to "configuration.archives.allArtifacts". > > It's not a bug, but more of a quirk of configurations modelling incoming > (dependencies) & outgoing (artifacts) right now (which is an Ivy hangover). > > In the way you're using it, configurations.archives is like saying > configurations.archives.dependencies > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
