Thanks Graham! I works this out just as I got your email :)
To explain this to others... taking a multi module maven project either out of svn/cvs (Q: outside eclipse only?) or creating one from scratch leaves you with a skeleton Maven project. With no eclipse .project/.classpath/.whatever files in the project, it can then be made "eclipse complient" with the "mvn eclipse:eclipse" command on the project parent. From this point onwards, the project source now contains all the Maven Information, Eclipse Information, and possibly svn/cvs. Now that you have content to import, you can "Import Existing Projects -> Maven Project" into Eclipse. With it will come the Maven, Eclipse and possibly svn/cvs information. The parent appears in the project list, as do the modules. I only have these closing questions/clarification... Performing checkout's outside the IDE, then running "mvn eclipse:eclipse", then importing is a bit of a pain.... to "get around this" would people (arguably no doubt) checkin the mvn eclipse:eclipse configuration into svn/cvs once generated? Or is it possible to checkout a parent, then run eclipse:eclipse within the IDE? Thanks again, Andrew On Mon, Feb 25, 2008 at 9:52 AM, Graham Leggett <[EMAIL PROTECTED]> wrote: > Andrew Hughes wrote: > > > The bottom line is that eclipse can't cope with specifically with the > > "parent" and "heirarchy" strucutre. You must checkout the whole parent > with > > command line (or a different IDE) and mvn install the parent to the > local > > repo.. > > Yep, not too far beyond most developers at this point... > > > then work on each module individually checked out in isolation. > > Why? > > Just run "mvn eclipse:eclipse" in the root of your multimodule project, > and then tell eclipse to "import existing projects" starting at the root > of the multi module project. > > Eclipse will import all projects regardless of any weird directory > structure you (or maven) might have imposed, and you can switch between > the projects at will, and have all of them loaded at once. > > Maven sets up all the eclipse projects in a multimodule build so that > each project depends directly on each other project in eclipse (as > opposed to modules depending on the final jar of another module). This > removes the need to run "mvn install" on one module before changes to it > are visible to other modules in the multimodule project. > > Yes, the original checkout will need to be done outside of eclipse using > a normal scm tool, but that's not beyond the skills of a developer is it? > > Regards, > Graham > -- >
