I'd like to lobby for a change in the default behavior of eclipse:eclipse, which currently configures Eclipse to put its output in the same place that maven does, under target/classes and so on.
Eclipse and maven don't treat the paths the same way, which, when they're sharing output folders, can lead to erratic behavior. As a specific example, XML files in src/main/java automatically get copied by Eclipse into the Eclipse output folder. Maven doesn't do this unless you also specify a <resource> that points to them. But, maven can find and use the files that Eclipse copies over. As a result, you can have maven builds that pass while Eclipse is running (and building automatically) but fail in other circumstances (or when you do 'mvn clean install'). Having just wasted an hour tracking that down, I'm curious what the reasons are for having the two muddled together. Is the idea to save disk space? Regards, Michael Prescott
