On Wed, May 4, 2011 at 1:20 PM, Eric Kolotyluk <[email protected]> wrote: >> I am not a fan of "flat" multimodule projects and don't use them. I >> know that things generally work OK with them but I would not be >> surprised if you run into issues. >> > I'm not a fan either, but it was the only way to get things to work with > Jazz RTC. I know IBM plan to fix the problems in RTC with nested Eclipse > projects as they have a lot of customers who are using Jazz and Maven > together.
Someone else had a similar problem with another IBM product, can't recall the details. One option is to just ditch the IDE embedded version control and go back to the command line/GUI interface of the host version control. That way you can have your hierarchical project structure. Another thing to remember is that eclipse also has problems with hierarchical projects. And the IBM stuff is based on eclipse. I know this process works with Eclipse 3.2.2 + The work around is to: * checkout the root project (which contains all sub-projects) * run mvn eclipse:eclipse * refresh your eclipse workspace * use the NAVIGATOR view and delete the .project file from your root project. * File Import > and select your root project * You should see your modules ready for import, if not then you forget to delete the .project file You will occasionally get out of sync between workspaces, so refresh them after checkin/checkout and maven command line invocations. You should be able to run Team > Sync at any of the projects, but it will work if you only do this from the root project. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
