Oh, so the case is when you have an API jar, and instead of having an API jar which is a bunch of interfaces that you both share, there is just an implementation JAR which implements the given API.
That's a broken design pattern. I believe it's out there, but that's really broken. ~~ Robert. On Wed, Jul 6, 2011 at 12:40 AM, cquinn <[email protected]> wrote: > If you declare the api libraru as 'compile', it will be inherited by > 'runtime' and be transitively brought in to all downstream builds, including > the final app's war or other archive. That could clash with the actual > implementation library that the app or container might be providing, > resulting in classpath problems. > > It seems like the current Gradle approach is to cancel out the unwanted > transitive compile/runtime using the war task's providedCompile conf. But, > if this is true, that seems like a bit of a kludge. Workable, but not > optimal. > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Ivy-vs-Gradle-configurations-tp4544242p4555689.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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
