On Wed, Apr 29, 2009 at 4:13 PM, Jörg Schaible <[email protected]> wrote: > Arnaud HERITIER wrote at Donnerstag, 16. April 2009 10:42: > >> Hi Community, >> 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? Since "mvn test" will fail with a different error than Eclipse with your suggestion. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
