Don't assume default project settings

[jsuereth]

When trying to run eclipse on a build that has a non-standard project, I get the following errors:

[error] Could not create Eclipse project files:
[error] Undefined setting 'name'!
[error] Undefined setting 'unmanaged-source-directories'!
[error] Undefined setting 'class-directory'!
[error] 
[error] 
[error] 
[error] Undefined setting 'unmanaged-source-directories'!
[error] Undefined setting 'class-directory'!
[error] 
[error] 
[error] 
[error] Undefined task 'external-dependency-classpath' for 'dist'!
[error] Undefined task 'update' for 'dist'!
[error] Undefined task 'update-classifiers' for 'dist'!
[error] Undefined task 'external-dependency-classpath' for 'dist'!
[error] Undefined task 'update' for 'dist'!
[error] Undefined task 'update-classifiers' for 'dist'!

This project is not meant to have update, external-dependency-classpath or even name. It doesn't compile class files. As such, it doesn't need eclipse settings files, it can just be ignored. It'd be ideal if the plugin allowed such projects to exist without negating the generation of settings for others.

[hseeberger]

Are you asking to ignore "invalid" projects? Could make sense.

In the meantime, please use EclipseKeys.skipProject := true for non-standard projects.

[jsuereth]

That's all well and good, except I don't want the eclipse plugin to invade my project's plugin space, but stay in the user directory. I've worked around it for now by adding the useless defaultSettings, but I'd prefer ignoring invalid projects and issuing a warning, or some global setting I can make rather than forcing the project to include the sbteclipse plugin....