Hi all, I know probably it's a silly question, but I don't fully understand why a combination or compile/runtime circular dependencies between two libraries determines a circular dependency between tasks. I know circular deps are evil, but sometimes we have to deal with them (especially when you cannot refactor).
I've tried the following configuration: - a multiproject build that includes prj1 and prj2. - both projects applies the java plugin - prj2 declares a *compile dependency* on prj1 - prj1 declares a *runtime dependency* on prj2 launching /gradle jar/ it fails complaining /Circular dependency between tasks. Cycle includes [task ':prj2:compileJava', task ':prj2:jar']./ /settings.gradle/ /prj1/build.gradle/ /prj2/build.gradle/ If I convert the compile dep to runtime it works fine. It seems like gradle tries to satisfy runtime deps for prj1 before making it available to compile prj2... maybe the runtime configuration should be processed in a different way? BTW is there a way to obtain the full task graph in this situation? Tried both with m3 and m5. Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/Why-runtime-involved-circular-dep-causes-circular-dependency-between-tasks-tp4875733p4875733.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
