Skip to content

Commit f8561ef

Browse files
committed
Use progress monitor when finding types in project
This allows for nested types to be resolved. Without a progress monitor, JDT doesn't resolve nested types. Signed-off-by: David Thompson <davthomp@redhat.com>
1 parent b8f2366 commit f8561ef

File tree

1 file changed

+2
-1
lines changed
  • qute.jdt/com.redhat.qute.jdt/src/main/java/com/redhat/qute/jdt/utils

1 file changed

+2
-1
lines changed

qute.jdt/com.redhat.qute.jdt/src/main/java/com/redhat/qute/jdt/utils/JDTTypeUtils.java

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@
1717
import java.util.logging.Logger;
1818

1919
import org.eclipse.core.runtime.IProgressMonitor;
20+
import org.eclipse.core.runtime.NullProgressMonitor;
2021
import org.eclipse.jdt.core.IField;
2122
import org.eclipse.jdt.core.IJavaProject;
2223
import org.eclipse.jdt.core.IMember;
@@ -48,7 +49,7 @@ public static String getSimpleClassName(String className) {
4849

4950
public static IType findType(IJavaProject project, String className) {
5051
try {
51-
return project.findType(className);
52+
return project.findType(className, new NullProgressMonitor());
5253
} catch (JavaModelException e) {
5354
LOGGER.log(Level.SEVERE, "Error while finding type for '" + className + "'.", e);
5455
return null;

0 commit comments

Comments
 (0)