Please, please don't propagate the Maven 'best practice' hierarchical only project layout. It's got nothing to do with eclipse itself, but the layouts of your projects in version control shouldn't be defined by your build tool.
I'm happy to set up svn:externals to let the build tool have the structure it wants, but it shouldn't force you to layout projects a particular way. Isn't that what the Convention should specify? On Tue, Jul 15, 2008 at 7:05 AM, Hans Dockter <[EMAIL PROTECTED]> wrote: > Hi Ignacio, > > On Jul 14, 2008, at 6:01 PM, Ignacio Coloma wrote: > >> >> Hi, I know this may have been asked previously but I could not find it in >> the >> forums or elsewhere. > > You are the first one on this list :) > >> >> How is it expected to integrate gradle multiproject with eclipse? Say I >> have >> "myproject", "myproject/A" and "myproject/B", which are fine with gradle, >> but eclipse needs all projects as direct children of the workspace, so you >> should checkout "A" and "B" directly into the workspace, where "myproject" >> files are _not_ located. >> >> Am I missing something? > > No. This is in fact a problem. Not just for Gradle, also for a couple of > Maven plugins. There are two ways to deal with this: > > - Change the multi-project layout: Right now Gradle only accepts > hierarchical layouts. In the near future we want to support arbitrary > multi-project layout. But right now you can't change the layout. > > - Tweak Eclipse: I have done this in in a large enterprise Maven build and > it has worked reliably. It works like this: > Provided there is a hierarchical project in svn. You check out the top level > dir into Eclipse as a non Java Project (Simple project). If the .project > Eclipse files are not in svn you have to generate them. As we don't provide > a plugin for generating Eclipse project files yet this has to be done by > hand. If the Eclipse project files of the subprojects are created you delete > the .project file of the top level project. Than you are able to import the > subprojects. After the import, as soon as you do some operations on the > top-level project, Eclipse creates the .project file again automatically. > But this is no problem, as you have already imported your subprojects. > Without deleting the .project file, Eclipse would not allow to import the > subprojects. It is big limitation of Eclipse not to support hierarchical > layouts. > > I can't offer you anything better at the moment. > > - Hans > >> >> Thanks in advance, >> >> Ignacio. >> -- >> View this message in context: >> http://www.nabble.com/Multiproject-with-eclipse-tp18447030p18447030.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 >> >> > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- dIon Gillard There are only two kinds of programming languages: those people always bitch about and those nobody uses. (Bjarne Stroustrup) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
