Hi We have just configured a shared Ivy repository which we managed to configure for "changing revisions". Our project setup is very modular with about six multi-module projects each with about four sub projects.
Within each multi-module project we use "project" dependencies between the subprojects, and normal dependencies for dependencies on modules from other multi-module projects. The problem is that we currently need to publish (uploadArchives) to the shared repository for a cross-multi-module dependency to be resolved, this isn't very good since that will then be picked up by other developers. What we want is the maven kind of install functionality which will install it into our local cache and make it available on my machine. Then when the artifact is ready I want to be able to "deploy" it to the shared repo for other devs to use. After writing all the above this was brought to my attention : http://jira.codehaus.org/browse/GRADLE-1014 http://gradle.1045684.n5.nabble.com/install-archive-jar-to-cache-td1431488.html Has anyone got a workaround for this? Cheers, Micke -- View this message in context: http://gradle.1045684.n5.nabble.com/How-do-I-emulate-the-maven-install-deploy-goals-using-Gradle-tp3377432p3377432.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
