I'd prefer to keep the .settings stuff on the wiki as exported xml files. Anyone using Eclipse could then import the xml files.
But I'm open to keeping the .settings file around, only problem would be if NetBeans or whatever decided they also used the same name directory and we had a conflict.
Either way is fine with me.
Not sure what best practice (or that there even is a set yet :-)
The M2 plugin for eclipse is cool and works fairly well. There is an incompatibility between mvn eclipse:eclipse and the plugin. When you do mvn eclipse:eclipse it fills the .classpath with references to M2_REPO/foo.jar but the plugin knows and understands your pom.xml file so all that is not needed. The way I manage it is to mvn eclipse:eclipse then delete all the M2_REPO stuff then add the M2 Library. Tedious until the plugin is updated (for all I know it already is, I'm just to lazy to figure out how to fix it so if anyone knows please let me know) but it works. And once you get the setup done the plugin is really cool allowing you to add and manage your dependencies etc.
http://m2eclipse.codehaus.org/
is the update site for the eclipse plugin.
TTFN,
-bd-
On Friday, July 21, 2006, at 11:22AM, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
>On Jul 21, 2006, at 8:08 AM, Bill Dudney wrote:
>
>> a) remove lib, dist, .classpath, .project, .settings
>
>BTW, the .settings dir contains lots of nice things for Eclipse, such
>as code formatting "standard" for Cayenne, the new class templates
>with Apache license headers, etc. It would be nice to preserve it.
>Also I don't see any harm in Eclipse project files.
>
>What's considered to be the "best practices" when working with
>Eclipse and Maven.
>
>Andrus
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Jul 21 2006 - 11:59:56 EDT