Eugene Kuleshov wrote: > >> Thus: I now have moduleA and moduleB in my workspace TWICE. >> > That is what I call cosmetic. :-) >
On its own, I agree. Eugene Kuleshov wrote: > >> Problems with having these modules twice: >> >> - They're too nested, so useless to begin with >> > Wouldn't it be less nesting if you open resources from nested modules > not from the parent project, but from within module projects? > Personally I kind of don't like word "useless". If it is useless, why > did you created so many folders to begin with? :-) > I didn't (I'm just interested in the root of my project1). So my whole point is to get rid of them ;-) Eugene Kuleshov wrote: > >> - Search will return duplicate results >> - Ctrl+Shift+R gives the same files twice >> > We'll see what we can do about those. > That'd be great! Eugene Kuleshov wrote: > > But in a mean time you can try > to manually mark those folders as "derived" from project properties / > Resource / Derived. > > Note, that derived resources still going to appear twice in > Synchonization view and commit dialog in Subclipse, but I don't see any > errors while committing both of them (it is committed only once when > using Subclipse 1.4.x). You can probably request an enhancement request > to be able to make Subclipse to ignore derived resources. > Well, there you go, that works just fine. I could have a Monkey script do this automatically, and we would close this issue altogether. Of course, I'd have to remember to re-run the script every time someone adds a module, but still, it's not too bad. Eugene Kuleshov wrote: > >> - "Link with Editor" not working in Package Explorer >> > This one I can't reproduce. Technically, same resource shown in > different subtrees actually have different path in workbench and from > what I see, Package Explorer in Eclipse 3.4 works just fine: > > /test-foo/test-module/src/main/resources/test.properties > /test-module/src/main/resources/test.properties > Well, strangely enough, I only have this problem for .java files (so far). It'll show the Java file with a different icons, AFAIK to indicate that it does not know this file as part of the workspace. http://www.nabble.com/file/p18698772/amount-java.jpg Eugene Kuleshov wrote: > >> - 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 >> > I would suggest to report this particular issue to checkstyle plugin. > It is unclear if we can do about it, but we surely would help checkstyle > developers to troubleshoot it if they need our help. > > I'll do so as soon as I properly understand what's all going on. Eugene Kuleshov wrote: > >> - Eclipse takes much longer to process things >> > Have you done the measurement, i.e. how many minutes is "much" and for > how big projects/workspace? > As posted elsewhere: time is the same. My bad. Eugene Kuleshov wrote: > > Are you using Subclipse 1.2 or 1.4 by any chance? > We do not use Subclipse. Eugene Kuleshov wrote: > >> 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. >> > I was suggesting a specialized filter (basically an extension in > m2eclipse plugin) that would know about Maven project structure. > Actually have this prototyped already, just need to implement few > corner cases, such as single multi-module project, modules using ".." > and multiple path segments, modules not imported into the Eclipse > workspace, etc. Who would imagined that those need to be handled, right? > Sounds like our project is a great test case for all that ;-) Eugene Kuleshov wrote: > >> 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. >> > I hope you are not blaming m2eclipse for checkstyle failures? It is > perfectly legitimate case to have nested projects in workspace that show > the same resources more then once (and it completely supported by > Eclipse since, at least since 3.3). > I was not aware of that. (Like I am not aware of many things.) Let me reiterate: thanks for your efforts. -- View this message in context: http://www.nabble.com/Exclude-modules-directories-tp17487783p18698772.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
