Community
Participate
Working Groups
We use Maven to build our projects. We use the Maven eclipse plugin to generate .classpath and .project files. For certain dependencies, we would like to be able to specify eclipse.dependency so that the Maven plugin generates <classpathentry kind="src"... instead of <classpathentry kind="var"... However, this causes problems if one user wants a "src" dependency, but another user may not have that project in their eclipse workspace, or open. The ideal solution to this problem would be to be able to specify a <classpathentry> element in the .classpath file that is a hybrid of the src and var types, where eclipse first tries to look for a source project in the workspace, and if it finds it, it uses it, but if it doesn't, eclipse falls back to a jar file for the entry. This would promote more flexible development, where everyone one the team doesn't have to have the same projects in their eclipse workspace.
Classpath containers are intended to encapsulate such differences. Feel free to define your own classpath container initializer implementation, and have it expand itself in whatever meets your requirements. Classpath container initializers are to be used to model libraries, JREs and plugin dependencies (amongst others). You may contribute one more flavor of container to match Maven semantics.
