One solution would be to use the maven plugin and SNAPSHOT versions. With the maven plugin you would run 'gradle install' in project1. That would install the artifact in your ~/.m2/repository directory.
Then you define the dependency in project2 as is. On Wed, Jun 15, 2011 at 4:54 PM, Mike Mills <[email protected]> wrote: > I am having trouble converting two separate ant projects to gradle. > The output of the first project is a dependency on the second project. > > Both projects are separate SVN checkouts, both projects will be > changed frequently during development and there is currently two > separate CI builds, one for each of the projects. > > So in the past I have checkout project1, then built it. Then checkout > project2 and then built that including the artifact from project1 on > the classpath. > > I am looking for the current way that these two projects can be linked > with gradle. > > My first thought was to simply declare the following dependency in > project2's build.gradle: > > dependencies { > compile group: "project1", name: "core", version: "1.0.0" > } > > The issue here is that once the core-1.0.0.jar file is resolved by > gradle and is added to the local gradle cache, no more uploaded > artifacts from project1 are picked up in project2 > > > My second thought was to create a "parent" build.gradle file where I > could wire the projects together, but this file would not be checked > into subversion and would make the CI build hard to implement. > > > How do people on this list cope with this situation? > > Kind regards, > > -Mike > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Learn from the past. Live in the present. Plan for the future. Blog: http://eric-berry.blogspot.com jEdit <http://www.jedit.org> - Programmer's Text Editor Bazaar <http://bazaar.canonical.com> - Version Control for Humans
