Not exactly. Yes m2eclipse show exactly what we have in the parent project and its modules. For exemple : project1 |-moduleA |-moduleB
With this project, when I'll import it using m2eclipse, I'll have 3 eclipse projects project1, moduleA, moduleB. But in project1 I'll see moduleA and moduleB as directories, thus if a developper change something in moduleA, the SCM plugin (subclipse for exemple) will mark project1 and moduleA as modified. If he also modified something in moduleB and he tries to commit the change from project1, he will be able to commit both changes from moduleA and B. It can be the cause of erroneous commits, that's why I would prefer to not see moduleA and moduleB in project1. Arnaud On Tue, May 27, 2008 at 2:29 PM, Igor Fedorenko <[EMAIL PROTECTED]> wrote: > Arnaud, > > Can you explain desired behaviour in better details? > > Currently, when you import multi-module project into m2eclipse, you can > either keep all modules in one eclipse project or create separate projects > for each module (the default). In both cases, however, m2e creates exactly > the same and single directory structure on the physical filesystem, so you > cannot have inconsistent changes in "parent" and "module" project. Does this > address your concerns? > > > Arnaud HERITIER wrote: > >> Hi guys, >> >> I just opened a new enhancement proposal to exclude in an aggregator >> project its submodules. >> http://jira.codehaus.org/browse/MNGECLIPSE-635 >> Do you think that it is possible in eclipse ? >> I didn't find a way to do it googling to exclude directories from an >> eclipse project :-( >> Arnaud >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
