It seems that the archives script block does not support declaring artifact by the archive task name that wasn't yet declared. Ideally, this should just work but it is not implemented at the moment. In general, the Gradle DSL support lazy evaluation in many aspects.
> I could not find anything in the documentation specifically about > ordering of definitions in the build file I think there's info on that matter in the user guide, yet there may not be a specific section for it. For example, at the begging the rules on task dependencies are described with ways of declaring a dependency on a task that was not yet declared. Cheers! On Sun, Jun 12, 2011 at 3:44 PM, Mike Mills <[email protected]> wrote: > I have got the following error when altering one of the samples: > > "No such property: myJar for class: > org.gradle.api.internal.artifacts.dsl.DefaultArtifactHandler" > > This occurs when the task is defined after the configuration and > artifacts section. Taking the samples/userguide/artifacts/upload > project as an example, change: > > task myJar(type: Jar) > artifacts { > archives myJar > } > > to: > > artifacts { > archives myJar > } > task myJar(type: Jar) > > and run gradle uploadArchives to reproduce. > > I could not find anything in the documentation specifically about > ordering of definitions in the build file, is there something I have > missed or is this just a bug? > > Thanks, > > -Mike > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
