I'm encountering this same issue; however I have "jar.enabled = true" in my project definition and it still skips the jar step.
Etienne Studer wrote: > > 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 >> applied in the documentation >> >> regards >> gretar >> >> On Fri, Oct 15, 2010 at 2:04 PM, Etienne Studer >> <[email protected]> wrote: >> 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 >> :processTestResources UP-TO-DATE >> :testClasses >> :test >> :check >> :build >> >> Regards, Etienne >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > Etienne Studer > Senior Software Developer > > Canoo Engineering AG > Kirschgartenstrasse 5 > CH-4051 Basel > > T +41 61 228 94 44 > F +41 61 228 94 49 > > [email protected] > www.canoo.com > > > > -- View this message in context: http://gradle.1045684.n5.nabble.com/jar-SKIPPED-tp3213728p3362096.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
