I just wanted to add to the discussion, that we are not perfectly happy how
the plugins work together at the moment. IThey don't have the quite the
right granularity. The Java plugin should not add a jar and a javadoc task.
That should be done by a lib plugin. If you want to have a war and a
Thanks. jar.enabled = true works fine. Sorry for having missed it in the
documentation.
Regards, Etienne
On 15.10.2010, at 17:23, Gretar Arnason wrote:
yes should be a property on the tasks
task.enabled = false
there is an example of how to enable jar task again with the 'war' module
Hi
When I apply the war plugin, the jar task is skipped, as shown by the output
below. Question: how does Gradle do this, i.e. what/who decides if a task is
skipped? A property on the task or...?
:compileJava
:processResources
:classes
:jar SKIPPED
:war
:assemble
:compileTestJava
err: 'war' plugin
On Fri, Oct 15, 2010 at 3:23 PM, Gretar Arnason gretarr...@gmail.comwrote:
yes should be a property on the tasks
task.enabled = false
there is an example of how to enable jar task again with the 'war' module
applied in the documentation
regards
gretar
On Fri, Oct
