Thanx Chris, I'm going to try this out tonight. I'm not sure I understand the import/disconnect and connect thing, though. Do you checkout from Eclipse or the Command line? If from Eclipse then I assume all of the folders come down at once? Is this where you disconnect the children and check them out in a different location? I've tried Subversive checking out only the parent w/o recursing, then checked out one of the children and that seems to work. Are there any potential pitfalls with this approach? I'd rather not refactor to a flat structure because I've read about an open bug regarding the release plugin with flat structures. Is that still an issue? Should we abandon the plug in all together and just use the cmd line? Should we use Subclipse or Subversive? All of these questions are nagging me. Thank you sooo much for any/all help on the matter.
-Cliff Chris Schmidt-3 wrote: > > I've gotten the project and submodules within eclipse by checking > everything out to the filesystem then doing an Import --> Maven Project. > A dialog should come up asking which modules to import into the > workspace. The only issue I've found is eclipse can't handle the > subversion configuration at the submodule level. I have to manually > disconnect the parent module from subversion before connecting the > children. I don't think that's a maven2 problem though. > > - Chris > > -----Original Message----- > From: Clifton [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 12, 2008 9:02 AM > To: [email protected] > Subject: Maven2Eclipse with multi-module projects? > > > Hello all, > > I am a devoted IntelliJ Idea user with Eclipse experience trying to get > my > team acclimated with Maven. I'm having trouble sharing a multi-module > Maven > project with my Eclipse brethren through Subversion. In Idea I can > merely > check out the project root folder and everything just works. However > I've > noticed several issues in Eclipse all regarding the m2eclipse plugin. > When I > check out the project using either Subclipse or Subversive I get the > option > to check out as a Maven2 project. Checking out from root does not bring > in > the child projects as Maven2 enabled projects. If I checkout the > projects > individually the m2Eclipse plugin then proceeds to define a new pom for > the > project upon checking out. This completely hoses the build path and gets > everybody confused as they have to manually redefine the pom and restore > the > dependencies. I've tried several attempts at checking out the project, > all > with no success. I've even tried the Q4E plug in which doesn't seem to > allow > me to configure an external Maven install or custom settings xml. What > is > the best practice for using Eclipse with a multi-module project? > -- > View this message in context: > http://www.nabble.com/Maven2Eclipse-with-multi-module-projects--tp154342 > 61s177p15434261.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven2Eclipse-with-multi-module-projects--tp15434261s177p15439144.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
