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.
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? > -- View this message in context: http://old.nabble.com/jar-task-disabled-when-war-plugin-included-tp28814297p28814302.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
