I opened this one few days ago : http://jira.codehaus.org/browse/MNGECLIPSE-635
Arnaud On Sun, Jun 1, 2008 at 4:57 PM, Tim Downey <[EMAIL PROTECTED]> wrote: > Yes. I think the simplest possible example would be a top-level > aggregating pom that builds some sub modules that are typically in > subdirectories of the aggregating pom. > > For example, you'd have a root folder / with a pom.xml. You may also have > /foo and /bar as submodules both normally built through the pom at /. > > The idea would be to allow the top-level pom to be imported into Eclipse > without having all the resources show up twice, once in the top-level > project and once in the sub projects. As it stands now, Eclipse gets all > gummed up with search and replace and certain refactorings because it finds > the resources in more than one place. > > > On Sun, Jun 1, 2008 at 10:53 AM, Mat Lowery <[EMAIL PROTECTED]> wrote: > >> I'm not positive that I understand the question but, leaving Eclipse out >> of it, we're using a "standard" multi-module Maven project where the parent >> project directory contains subdirectories for each of the modules. In other >> words, nested. >> >> But your question regarded Package Explorer. Are you suggesting that >> there's a way to tweak the presentation in Package Explorer, regardless of >> the layout on disk? >> >> Thanks again! >> >> On Sun, 2008-06-01 at 10:40 -0400, Eugene Kuleshov wrote: >> >> BTW, are you guys using flat or hierarchical presentation for the >> Package Explorer view? >> >> >
