I would like to have the following structure for my projects: -D ProjectsDir -DProject1 -DProject2 -Dbuilds The reason for this is that the projectsDir is to be my main CVS directory, and this way my build logic can be a module rather than a set of files in the top-level directory. I would otherwise have to declare settings, properties, and build each as modules for a CIS app to pull them for builds, as well as any gradlewrapper files. If they change names, I have to go redeclare them in the continuous integration configuration. First, I changed the included projects to ../ and it found them, but then project dependencies cannot be resolved. If I change the project dependencies to ../ it gets a little further but breaks on the error:
java.io.FileNotFoundException: C:\Documents and Settings\user\.gradle\cache\resolved-org.gradle-..\Project1-1.0.xml (the system cannot find the file specified) in buildscript Is there a way to do this? Thanks for any help... Jerod -- View this message in context: http://www.nabble.com/non-top-level-project-root-tp18157915p18157915.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
