eclipse project metadata in trunk not generic

[GoogleCodeExporter]

Import project via maven eclipse plugin, and you end up with some builders that 
are pulled in 
because of existing eclipse metadata.  Specifically the ANTLR eclipse builder 
jobs have references 
to ${M2REPO} and {workspace_loc:/testability-explorer-core} neither of which 
exist.  

The former can be set up as a library if desired, and the latter doesn't work 
because m2eclipse 
names the project after the artifactId, so it should be {workspace_loc:/core}

But in fact, I wonder if having the eclipse metadata in svn is the right answer 
at all?  I'd rather 
remove it, because eclipse metadata tends to badly blend user-specific and 
project specific 
settings (just pay attention to your .settings folder in some projects - total 
mix of personal and 
project metadata).  It becomes very hard to version and not clobber each other.

So I recommend removing .project, .classpath, and .settings entirely from svn 
and svn:ignore-ing 
them.

Original issue reported on code.google.com by christia...@gmail.com on 23 Apr 2009 at 7:14

[GoogleCodeExporter]

Sorry... and .externalToolBuilders/

Or check them into an alternate folder like /eclipse/.* with a README that says 
copy these into the root on your 
local workspace if you want a quick way to open in eclipse.

Original comment by christia...@gmail.com on 23 Apr 2009 at 7:18

[GoogleCodeExporter]

I don't use eclipse, so I don't update the metadata files when I make maven 
changes,
and so sometimes the eclipse setup doesn't work out of the box for other people.

+1 for removing it

Original comment by aeagle22206 on 24 Apr 2009 at 2:18