I always run Eclipse and ant/maven pointing to the same place. Sure, clean means you have to do a rebuild in Eclipse, but you don't actually have to do clean that often. On the other hand, pointing to the same place means that you can have maven build rules (in maven.xml or wherever) that output things (transformes properties file, resources, etc.) to the build directory that Eclipse couldn't handle building itself and putting there. This means you can then run unit tests properly, etc. So Maven does the 'real' build, but Eclipse can happilly co-exist, and handle some sorts of tasks, such as taking java source and producing class files.
I would suggest leaving it the same by default, and adding an option to make it something else. At the end of the day, the plugin is about taking a Maven project and making Eclipse work with it. If you set the output directory somewhere else, then effectively you totally separate Eclipse and Maven.
James Strachan wrote:
The eclipse plugin currently sets the target directory for eclipse's build to target/classes. I just wanted to get feedback from other Eclipse users about this. I'd prefer Eclipse to have its own output directory; preferably in something different like bin.
Basically I like to do lots of
maven clean test
from time to time. Any 'maven clean' will force a rebuild to be required in eclipse. So I don't see much value in Eclipse's binary compilation of the code to be in the same place as where Maven builds. I'd prefer to keep them separate.
IDEs are notoriously subjective - would this approach suite others use of Eclipse? If so I'll go ahead and patch the eclipse plugin to not use the same location as Maven for its build files.
James -------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
