Community
Participate
Working Groups
JDK1.5.0b1, Cheetah04. Created a new JUnit launch configuration ('Run all tests in the selected...'), run it -> it fails with the "Internal error" message. Log file contains the following: !ENTRY org.eclipse.core.runtime 4 2 Apr 27, 2004 14:04:30.812 !MESSAGE An internal error occurred during: "Launching". !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.resolveTypesFor (SourceTypeBinding.java:799) at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.methods (SourceTypeBinding.java:692) at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.getMethods (SourceTypeBinding.java:582) at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.getExactMethod (SourceTypeBinding.java:518) at org.eclipse.jdt.internal.compiler.lookup.Scope.findExactMethod (Scope.java:427) at org.eclipse.jdt.internal.compiler.lookup.Scope.getMethod (Scope.java:1481) at org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType (MessageSend.java:253) at org.eclipse.jdt.internal.compiler.ast.Expression.resolve (Expression.java:438) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolveStatement s(AbstractMethodDeclaration.java:383) at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements (MethodDeclaration.java:133) at org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve (AbstractMethodDeclaration.java:360) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve (TypeDeclaration.java:925) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.resolve (TypeDeclaration.java:974) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.resolve (CompilationUnitDeclaration.java:280) at org.eclipse.jdt.internal.core.search.matching.MatchLocator.process (MatchLocator.java:1099) at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches (MatchLocator.java:739) at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches (MatchLocator.java:770) at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches (MatchLocator.java:867) at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches (JavaSearchParticipant.java:100) at org.eclipse.jdt.core.search.SearchEngine.findMatches (SearchEngine.java:468) at org.eclipse.jdt.core.search.SearchEngine.search (SearchEngine.java:760) at org.eclipse.jdt.core.search.SearchEngine.search (SearchEngine.java:728) at org.eclipse.jdt.internal.junit.util.TestSearchEngine.searchMethod (TestSearchEngine.java:98) at org.eclipse.jdt.internal.junit.util.TestSearchEngine.searchMethod (TestSearchEngine.java:89) at org.eclipse.jdt.internal.junit.util.TestSearchEngine.searchSuiteMethods (TestSearchEngine.java:175) at org.eclipse.jdt.internal.junit.util.TestSearchEngine.collectTypes (TestSearchEngine.java:155) at org.eclipse.jdt.internal.junit.util.TestSearchEngine.doFindTests (TestSearchEngine.java:122) at org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfiguration.findTestsIn Container(JUnitBaseLaunchConfiguration.java:125) at org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfiguration.getTestType s(JUnitBaseLaunchConfiguration.java:112) at org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfiguration.launch (JUnitBaseLaunchConfiguration.java:59) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:569) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:150) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch (DebugUIPlugin.java:780) at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run (DebugUIPlugin.java:966) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
The search support has been leveraged yet for 1.5 support. Remember that for now the Cheetah mostly focuses on compiler (which is the core piece). Down the road we will update all tools based on it, like the search engine.
Rein, do you still have the problem with Cheetah06 ?
Please reopen if you still have the problem. Steps to reproduce the problem would be welcome.
