Szczepan Faber wrote: > > The reason I want to have a > project dependency inside the IDE is that the changes are picked up > immediately. If I need to run 'gradle assemble' for the dependency > project to work with the latest changes I can as easily run 'gradle > install' (provided I use maven plugin and use mavenLocal() to share > intra-project dependencies). But then we're back at the starting point > of the discussion. > Just wondering if in the meantime we could - just as a raw workaround even for http://issues.gradle.org/browse/GRADLE-1014 GRADLE-1014 - intercept the dependency resolution (with a custom resolver?) and search within the rootProject subprojects if there is one having a compatible groupId/artifactId/version. If found, invoking the maven install task, then leaving the resolution process continue. This way we get some sort of raw automatic dependency resolution against projects (although deep IDE integration remains far, far away).
Cheers Davide -- View this message in context: http://gradle.1045684.n5.nabble.com/Is-it-possible-to-elect-a-local-gradle-project-to-satisfy-other-projects-deps-tp4497854p4774967.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
