I'll let Hans or Adam be the definitive, but I believe the idea here was that in a war project you're typical final output is a war file, not a jar. For the majority of the cases, this is probably true.
On Tue, Jun 8, 2010 at 01:46, vincer <[email protected]> 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. > > > 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 > > > -- Jason Porter Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
