On 17/06/2011, at 6:49 PM, Mirko Schroeder wrote: > 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.
How have you separated them? > 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. What configuration do you assign the artifacts from these other tasks too? There is a task rule to build each configuration: build«Configuration». So if you assigned the artifacts of your other tasks to their own configuration, let's say “site”, you could just build the library by… buildArchives (archives is the configuration that the Java plugin sets up for the jar task) And then build your site separately with buildSite > 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? I don't quite follow what you mean here. Can you elaborate? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com Please vote Gradle for JAX Awards » http://vote.jax-awards.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
