Skipped dependency with eclipse.dependency false

I would expect eclipse.plugin=false to behave af if the eclipse.plugin property wasn't set at all. Chances are I'm wrong about this, but I couldn't find any documentation that contradicts me.

When I trace it back to the source code, it's this 'when' in classpath.jelly that makes it skip the dependency entirely:

<j:when test="${eclipseDependency == 'false'}">-->
<!-- ignore specific dependencies -->
</j:when>

Again, I'm not too sure it should be doing this. When I take these lines out the dependency is treated as if eclipse.dependency isn't set at all: <classpathentry kind="var" in .classpath and <projects> in .project is empty.

(Eric Pugh)
I think the idea of eclipse.dependency is to filter out completely those dependencies.. The options are true/false, and default to true. So, if the eclipse.dependency is skipped, that is the same as true.

It is possible we need to have something more like:
eclipse.dependencyType that specifies what something is...

Eric

I can't see any valid use case why the eclipse project should not contain dependencies needed when building using maven.
Closing as a won't fix, please reopen the bug if you think this could be needed and post a valid use case.