Hey On Fri, Jun 17, 2011 at 10:49 AM, Mirko Schroeder <[email protected]> wrote: > Hello, as far as I understood the "assemble" task provided by the java plugin > depends automatically on all archive tasks in the project.
That's right. > > Now I've separated the build into several parts as there are the > main/default build, the site build, and some other useful tasks nothing to > do with the actual build. > > There are some archive tasks in the project, e.g. javadoc for the site build > which should not be executed during the main/default build but only for the > site build. You're in control what is the 'default build' via the 'defaultTasks' configuration. > > Wouldn't it be nice if the implicit dependency (depends on all tasks of type > archive) could be expressed explicitly just by adding the dependency > manually? It's the matter of how much CoC VS explicitness and I would say it's always debatable :) > > Or how can I exclude/remove the dependency than? assemble.dependsOn = [jar, xxx] The alternative for your use case is a set of neatly described tasks (see the "group" and "description" properites) and configuration of the defaultTasks. Cheers! > Thanks, > Mirko > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/assemble-task-tp4498158p4498158.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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
