Hi guys, I'd like to know if there is a way to somewhat elect a local gradle project to be considered for satisfying other projects dependencies. This way we could - especially on early developments - avoid packaging and uploading snapshot artifacts over and over on our private maven repo only to see how they behave on a project we have in the same workspace. This scenario applies even for testing a high invasive refactoring. It would be something similar to inline plugins for grails ( http://johnrellis.blogspot.com/2010/03/grails-inplace-plugin-tip.html ). PS: I asked the same thing to STS/gradle integration developers (they really made a great work!!!) at https://issuetracker.springsource.com/browse/STS-1314?focusedCommentId=41768&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-41768 but they forwarded me to this forum.
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-tp4497854p4497854.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
