Hi Andres, if you add to your /client|server/build.gradle/ you will see that the dependency is always resolved with the jar... no matter if it is not generated at all. In fact - as you pointed out - you see something like / Skipping task ':shared:jar' as task onlyIf is false. ... dropping /path/to/shared/build/libs/shared.jar from path as it doesn't exist /when you launch gradle with debug level set to logging.
I think it would be useful if gradle could resolve http://www.gradle.org/releases/1.0-milestone-6/docs/userguide/dependency_management.html#sub:project_dependencies compilation project dependencies against the output folder, at least when the jar is not generated at all. This could be useful for gwt compilation. My co-worker Mauro filed a partially correlated issue at http://issues.gradle.org/browse/GRADLE-1913 GRADLE-1913 . BTW I think an issue dedicated to your test case would be more appropriate (and I'd be happy to vote for it). In the meantime, adding something like should suffice as a workaround. Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/Why-runtime-involved-circular-dep-causes-circular-dependency-between-tasks-tp4875733p5031544.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
