Yep. That did the trick. I was thinking that only providedRuntime contained the providedCompile dependencies (didn't realize it was in runtime as well).
-Spencer --- On Thu, 2/3/11, Adam Murdoch <[email protected]> wrote: From: Adam Murdoch <[email protected]> Subject: Re: [gradle-user] Re: :jar SKIPPED To: [email protected] Date: Thursday, February 3, 2011, 3:45 PM Try: jar.enabled = true war { classpath = jar.outputs.files + configurations.runtime - configurations.providedRuntime } On 04/02/2011, at 7:24 AM, Spencer Allain wrote: Attempted to try this out, but got some strange behavior: provideCompile jar files started getting inserted into the war unexpectedly. -Spencer --- On Mon, 1/31/11, Adam Murdoch <[email protected]> wrote: From: Adam Murdoch <[email protected]> Subject: Re: [gradle-user] Re: :jar SKIPPED To: [email protected] Date: Monday, January 31, 2011, 9:29 PM On 01/02/2011, at 1:40 AM, StormeHawke wrote: Peter Niederwieser wrote: You need to provide some more information; otherwise it's just guessing on my side. Are the Hibernate config files located in the war project, or in some other project? As I mentioned I got the jar portion working; What I'm trying to figure out is how to convince the war task to include the projects own jar file in its lib directory. Is this possible? You could do this: jar.enabled = true war { classpath = jar.outputs.files + configurations.runtime} -- View this message in context: http://gradle.1045684.n5.nabble.com/jar-SKIPPED-tp3213728p3364662.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 --Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz --Adam Murdoch Gradle Developer http://www.gradle.org CTO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz
