Project: JDT
Bug 140553 [junit] New JUnit launch configs mapped onto wrong existing ones
Reported: 2006-05-08 09:12:36 | Status: verified fixed

3.2 RC3 When starting a JUnit test via (context) menu it first tries to find an existing launch configuration. The code that does the matching does not take the loader into account and hence unexpected results can happen, e.g. saying that no tests are found even though there are tests. For 3.2 we either need to fix the code which matches launch configurations or put this into the readme.

Files changed in fix:
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitMessages.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/launcher/TestKindRegistry.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitBaseLaunchConfiguration.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitLaunchShortcut.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/TestKindRegistry.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitMessages.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java