can it be true! A question I might be able to answer!
i have a multi project setup, working, and basically I call gradle on path
which holds nothing but the settings file.
The settings file is what directs the build to the various directories.
But the setting file, so far as I am aware, needs to be in the root.
So, you can have a setup:
./dev
./dev/settings.gradle
./dev/project1
./dev/somefolder/project2
./dev/someotherfolder/anotherfolder/project3
and in your settings file you'd have something like:
include "project1", "somefolder/project2",
"someotherfolder/anotherfolder/project3"
and in your gradle build files for the projects, you can refer to them like:
compile project(':somefolder/project2')
compile project(':someotherfolder/anotherfolder/project3')
Hope this helps,
if not, i'm sure the guys at gradle have better advise,
sean
On 30 May 2011 18:35, Thibault Delor <[email protected]> wrote:
> Hello,
> I have a project which is a library used by all the company. This
> project is build thanks to gradle. I have an other project in a
> complete different folder that depends on this project. I don't
> succeed in expressing this dependency with gradle. I have the feeling
> that multi-project works only if all projects are in the same folders.
>
> What can i do?
>
> Best regards,
> Thibault Delor
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
