Btw, the other thing I think the plugin needs (which I will probably do eventually if it doesn't show up), is a way to generate the info to files other than the existing .project and .classpath. If you have existing eclipse project files in the dir, you don't want them blown away, but on the other hand it is very useful to run the plugin so that you can regenerate the dependencies and manually cut and paste them into the eclipse .classpath file.


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
-------
http://radio.weblogs.com/0112098/





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to