On 16/04/2011, at 2:07 AM, Luke Taylor wrote: > On 15/04/2011 15:22, John Murph wrote: >> On Thu, Apr 14, 2011 at 10:59 PM, Adam Murdoch >> <[email protected] <mailto:[email protected]>> wrote: >> >> >> On 15/04/2011, at 1:59 AM, Jason Porter wrote: >> >>> Has there been any work done on this issue (providedCompile >>> outside of war projects)? I see Hans said this would be a 1.0 >>> thing, and probably something to do with the publishing API rework. >> >> I'm not sure we want to do this, at least not without a good use >> case. Do you have an example of why you want a provideCompile >> configuration? >> >> >> >> I'll just chime in that we also have a need for this. It's easy enough >> to solve (we have a "provided" custom configuration we are using), but >> it seems common enough that Gradle should provide this right out of the >> box. >> > > We also have a "provided" configuration and it seems like a common > requirement. Lots of project modules are compiled against the > servlet-api, even though they aren't actually WAR files, and you don't > want it exported as a transitive dependency.
But why not? It is actually a runtime dependency of the code, isn't it? -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
