>>>> The recent release 2.6 of the maven-eclipse-plugin created many problems >>>> for all of those who had/wanted to store non-java files under src/*/java >>>> (which is required for wicket, ajdt, and probably others usecases). >>>> Even we have many integration tests in this plugin we didn't notice this >>>> issue because our testcases allow us to check that generated >>>> configuration files aren't evolving and that we are able to import and >>>> use a project in eclipse (too heavy to do). >>> Regarding the new classpath ordering invented with 2.6, can you please >>> comment again in MECLIPSE-544 for my proposal (I mention it here, since >>> the issue is already closed). A classpath order like >>> >>> src/test/resource >>> src/main/java >>> src/test/java >>> src/main/resource >>> >>> Will solve also the test "resources first" problem. Since Eclipse will >>> complain anyway if you have to classes with the same name in >>> src/main/java and src/test/java, their order does not really matter for >>> Eclipse projects. >> What is wrong with having a classpath that matches Maven? > > Because every developer I've seen using the new plugin immediately thinks > something is broken after refreshing the IDE. And when you explain them the > situation, most of them moan about opening always the wrong node looking > for the code. Actually, it is confusing, since Maven projects are now even > more alienated in Eclipse as usual.
Noting beats correctness! I'd say let developers moan for a while, they'll get used to the classpath ordering. Besides that: I hardly don't use any kind of explorer in Eclipse any more. Any project with a non-trivial codebase can be better handled opening types directly through Ctrl-Shift-T. But that's just my personal way of working... -dirk --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
