Hi Marshall, 2010/12/13 Marshall Schor <[email protected]>
> When using m2eclipse, this is not particularly an issue (I think) - other > than > it takes up vertical space in the explorer view to show those contained > projects. > > I've gone back and forth about this, myself, and wonder if others have > opinions > on it? I've done some experimenting, and, at least for me, the M2eclipse > preference "hide folders of physically nested modules" doesn't hide them > (Eclipse 3.6.1, m2eclipse 0.12.0). Also, I've observed that the svn > changed > flags show up on both "views" of the same folder, if there is a change. > > to work with Maven multimodule projects I usually use the File -> Import -> Existing Maven Project -> select the parent folder and then check all the modules (one for each pom). This way you have one separate project for each module and also one parent project in which modules' build paths are not set so in that you see only the parent POM and the modules directory structures. Also in that way modifying files on a module project is automatically synchronized with the same file in the parent project. So in this way you don't have the whole "vertical" structure in one project (when enabling nested modules) and can work on modules separately. Lately I've been working with IntelliJ Idea for a while and I find it quite better in support to multi module Maven projects; however we'd need someone working on IntelliJ Idea UIMA plugins to provide a better experience there too. Cheers, Tommaso
