Creating right classpath for Eclipse import


When using the Eclipse plugin, I have the same problem has when using Maven import : all dependencies are flatten, ie compile, test runtime all become compile dependencies. Even worst, all transitive dependencies become direct (compile) dependencies.

The expected result would be to keep only direct compile dependencies, and to create a launcher with the runtime and transitive dependencies.

But this problem is so acute (in fact, it makes the whole thing totally unusable) that I feel I must be missing something. But what ?

What you describe is the way I’ve always seen people work with Eclipse, and it’s the only way that’s currently supported by the Eclipse plugin. The situation is somewhat better for IDEA, which understands the concept of ‘dependency scope’.