Eugene Kuleshov wrote: > > Can you please elaborate little more what problems exactly you have > with same folders shown more then once in Package Explorer? It seem like > more a cosmetic and perhaps a bit confusing issue. Is there any harm in > it? Can you please explain little more and maybe provide a sequence of > steps that would demonstrate erroneous behavior? >
It's not just cosmetic, but it's not blocking either. Somewhere in the middle, I suppose ;-) Given the following project structure (borrowed it from Arnaud), where project1 is the aggregator and parent of moduleA and moduleB: project1 |---moduleA `---moduleB In Eclipse, without nested modules, they'll show up as follows: project1 |---<closed> moduleA |---src/main/... |---JRE System Library |---Maven Dependencies |---.settings |---src |---target-eclipse |---.checkstyle |---.classpatch |---.project `---pom.xml moduleB |---src/main/... |---JRE System Library |---Maven Dependencies |---.settings |---src |---target-eclipse |---.checkstyle |---.classpatch |---.project `---pom.xml Above, I had my project1 closed. Eclipse is now error free. Following, I open project1. It'll show up as follows: project1 |---JRE System Library |---Maven Dependencies |---.settings |---moduleA | |---.settings | |---src | | |---main | | | |---java | | | | `---com | | | | `---wps | | | | ... | | | `---resources | | | ... | | `---test | | ... | |---target-eclipse | |---.checkstyle | |---.classpatch | |---.project | `---pom.xml |---moduleB | |---.settings | |---src | |---target-eclipse | |---.checkstyle | |---.classpatch | |---.project | `---pom.xml |---target-eclipse |---.checkstyle |---.classpatch |---.project `---pom.xml Thus: I now have moduleA and moduleB in my workspace TWICE. Problems with having these modules twice: - They're too nested, so useless to begin with - Search will return duplicate results - Ctrl+Shift+R gives the same files twice - "Link with Editor" not working in Package Explorer - Getting Checkstyle exceptions, "java.lang.RuntimeException: Unable to get class information for @throws tag 'XxxException'". We already got those exceptions a lot, but on moduleA and moduleB we're able to get rid of them with the "Check Code with Checkstyle" command, which does not work for project1 - Eclipse takes much longer to process things It appears that applying a filter doesn't do the trick: adding "moduleA" to the "Name filter patterns" will remove it from both instances, not just the one below project1. Our current workaround is to simply leave project1 closed. But I feel this is just a workaround, not a solution. More surprisingly, I does not even get rid of the Checkstyle exceptions. Well, perhaps that's because the filters only apply to the Package Explorer, and not to the Navigator. -- View this message in context: http://www.nabble.com/Exclude-modules-directories-tp17487783p18679251.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
