Community
Participate
Working Groups
Using 3.0.1 RC2. Looking at bug 71267, I tried to perform a search of package p declaration and got following NPE stack trace: An internal error occurred during: "Java Search". java.lang.NullPointerException org.eclipse.jdt.internal.ui.search.NewSearchResultCollector.acceptSearchMatch(NewSearchResultCollector.java:31) org.eclipse.jdt.internal.core.search.matching.MatchLocator.report(MatchLocator.java:1199) org.eclipse.jdt.internal.core.search.matching.MatchLocator.locatePackageDeclarations(MatchLocator.java:929) org.eclipse.jdt.internal.core.search.matching.MatchLocator.locatePackageDeclarations(MatchLocator.java:912) org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:99) org.eclipse.jdt.core.search.SearchEngine.findMatches(SearchEngine.java:468) org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:757) org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:125) org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:83) org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Although NPE was in JDT/UI land, it comes from JDT/Core... MatchLocator.newDeclarationMatch( IJavaElement element, int accuracy, int offset, int length, SearchParticipant participant, IResource resource) method returns null as it seems that no match was instanciated for PackageDeclaration element type...
Fixed and released in HEAD. This bug will be targeted for 3.0.2 when available and released in R3_0_maintenance stream after 3.0.1 is shipped... Now package declaration can be searched without any error and returns correct result. [jdt-core-internal] Changes done in MatchLocator.newDeclaration(...) method. Test cases added in JavaSearchTests
Fixed and released in R3_0_maintenance stream. Bug Target still needs to be set to 3.0.2 when it will be available...
Setting target to 3.1 M2 while waiting for 3.0.2 one...
Verified in I200409230100.
Finally set status as VERIFIED. We'll only change target when fix will be definitely put in R3_0_maintenance stream...
Candidating fix for 3.0.2 release (not committed yet)
Verified with M20050216