Likely, you'll want to do what we've done.
war {
classpath = jar.outputs.files + configurations.runtime -
configurations.providedRuntime
}
I suppose this functionality should be added to the core war plugin so
that the user can choose which behavior is desired, but it'd have to be a bit
more cooperative with the jar functionality.
-Spencer
--- On Fri, 5/20/11, Rene Groeschke <[email protected]> wrote:
From: Rene Groeschke <[email protected]>
Subject: Re: [gradle-user] 'jar.enabled=true' doesn't work in war plugin
To: [email protected]
Date: Friday, May 20, 2011, 6:20 AM
Hi Xiaojian,
the expression:
-----
jar.enabled = true
-----
does not mean that the classes are packed as a jar into the web-inf folder of
the war file. It just means that the jar task is enabled and in addition to the
war a plain old jar file with the classes of the project is created too.
regards,
René
Am 20.05.11 11:46, schrieb Xiaojian Ao:
> Hi
>
> In gradle userguide, I got that "war plugin will disable the default JAR
>archive generation of the Java plugin", and to change this action, we can set
>"jar.enabled = true".
>
> But I have test in my script, when I add "jar.enabled = true" to
>build.gradle, the classes of current project are still copied to
>WEB-INF/classes as java class file, not
> package to a jar and move to WEB-INF/lib.
>
> My env: gradle1.0-M3, windows vista, jdk 6.
>
> Can somebody help to comfirm this ? If true, I would like to add a jira
>bug for this problem.
>
> Sky Ao
-- -----------------------
regards René
rene groeschke
http://www.breskeby.com
@breskeby
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
