+1 for filtering duplicate resources. I typically use a hierarchical presentation.
I may have the time to look into adding the feature if you can point me in the right direction. I haven't looked at writing Eclipse plugins in quite some time. On Sun, Jun 1, 2008 at 10:40 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > > We believe that using separate projects allow much more flexibility for > configuring projects, especially when you have to enable AJDT, WTP and other > Eclipse tools. More over, with multiple projects we can match Maven > classpath to what JDT is using much better. Also note that issues wit nested > projects in Subclipse been fixed in version 1.3.x, which been available for > a while as dev builds and going to be released somewhere soon along with > Subversion 1.5 release it is based on. > > As for resources shown multiple times, please open an enhancement request > in JIRA for this, it shouldn't be that difficult to add filter for this > using org.eclipse.jdt.ui.javaElementFilters extension point (if anyone > interested to work on that please let us know). > > BTW, are you guys using flat or hierarchical presentation for the Package > Explorer view? > > regards, > Eugene > > > > Christian Edward Gruber wrote: > >> 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 > > >
