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 --
smime.p7s
Description: S/MIME Cryptographic Signature
