Mark wants this.

A fundamental problem is that for each examples module, there are 3 DIFFERENT eclipse configurations:
A) development: regenerated often by m2eclipse (or mvn eclipse:eclipse) - uses ~/.m2/repository jars.
B) distribution zip for people with the drools eclipse plugin: should rely on the drools eclipse plugin by adding a build command for org.drools.eclipse.droolsbuilder.
C) distribution zip without drools eclipse plugin: should NOT rely on the drools eclipse plugin. Uses ../lib/*.jars if needed.

Solution proposals:
1) No .project/classpath next to drools-examples/pom.xml (so gitignore them, let them generate A = current situation)
Create drools-distribution/src/main/assembly-resources/drools-examples/.project and .classpath to copy to drools-examples in the zip, which suffices for B.
Do not include any ../lib/*.jars (and definitely not ~/.m2/repository jars), instead just rely on the drools eclipse plugin to put those in the classpath.
Users of category C are not helped.
2) During building the drools-distribution, somehow generate the .project and .classpath to include all dependencies from ../lib/*.jars (including transitive dependencies without having to specify them).
3) Just wait a little bit longer until m2eclipse is part of the default eclipse distribution. Since the pom.xml files are there already, this becomes a none issue as they'll just open the pom.xml files (like in IntelliJ).