On 8/06/10 5:46 PM, vincer wrote:
Never mind, just found the reference to jar.enabled=true in the docs. I'm
still curious as to why this defaults to off though.
It's pretty much historical. At some point soon we will revisit this and
stop disabling the jar. We could enable it now, but we want to first
make some changes to the dependency/publishing DSL so that the jar is
only built when it is actually needed (by another project, for example).
vincer wrote:
It took me a while but I finally found that the jar task is explicitly
being disabled when the war plugin is included (the error message
"Skipping execution as task onlyIf is false." wasn't very helpful).
What's the reasoning behind this? Is my only option to define a new jar
task?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
CTO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
