I think the answer isn't to uncheck it, because having each maven
project be an eclipse project is a better line-up. However, having
the eclipse maven plugin hide those modules in the parent project that
are current projects in the workspace would be good. That would
eliminate the duplication.
Christian.
On 31-May-08, at 19:20 , Mat Lowery wrote:
When using the "Check out as Maven project" option within Subclipse,
there is a checkbox labeled "Separate projects for modules." By
default,
it's checked. In my experience, Eclipse behaves better when this
checkbox is unchecked. Why is this the default? Here are the
issues I
have with m2eclipse when Separate projects for modules is checked (and
I'm working with a multi-module project (nested layout)):
* Source trees show up twice in Package Explorer.
* Opening a .java file from one tree yields different behavior than
opening the source file from the other tree. Example: code
completion is
disabled in one and works perfectly in the other.
* Synchronization issues in Subclipse.
All of these go away (well, the source trees are still shown twice but
they're empty) when "Separate projects for modules" is unchecked!
Comments?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
