3

I am running Eclipse Luna on OS X 10.10.2. I have a project, which has somewhat recently had a Maven nature introduced. How can I configure a particular JUnit run configuration Classpath so that it uses the enclosing project's "default classpath" instead of Maven Dependencies? Every time I try to define or update (via "Restore Default Entries") the JUnit run classpath configuration, an empty project entry is added, then an empty Maven Dependencies entry, as illustrated by this screenshot.

Maven Dependencies always added

What I want is to not use Maven Dependencies, but rather just the default project classpath, which would be configured normally for this type of run configuration, as illustrated by this screenshot.

normal "default classpath" run config

I have tried disabling the Maven project nature entirely, to no avail (the blank Maven Dependencies are still added). I have also tried, to no avail, to find the IDE option to add project with default classpath, but perhaps that is what the "Restore Default Entries" button is supposed to do.

How can I force the JUnit run configuration to not use Maven Dependencies, but instead simply the default project classpath?

Jeff Evans
  • 1,257
  • 1
  • 15
  • 31
  • What's the context to your question? Is this project migrating to using Maven as a build tool? It seems odd for your project to have a Maven nature, yet you don't want to use the Maven test classpath. – Duncan Jones Mar 10 '15 at 07:53
  • We are evaluating Maven for use in a shared project. I want to stress again that the issue I described above continues to occur even after disabling the Maven nature from the project. – Jeff Evans Mar 10 '15 at 15:14

0 Answers0