On Fri, May 29, 2009 at 7:25 AM, Pete Muir <pmuir(a)redhat.com> wrote:
Ok, I found it in parent - any reason for this odd layout?
As I was saying before, this technique was an established crutch to help
Eclipse deal with Maven in the pre-m2eclipse days. Eclipse cannot have
nested projects. Therefore, when you use eclipse:eclipse, the parent gets
excluded from your Eclipse workspace and you can't edit the pom.xml file
there or use the Team support for SVN update. So, developers established
this workaround by positioning the parent adjacent to modules so everything
makes it into Eclipse.
But now that m2eclipse allows for nested projects, we don't need this
Senior Software Engineer, Red Hat | Author of Seam in Action
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.