After migrating to 0.9.12, Getting exception : org.reflections.RflectionException: Scanner SubTypeScanner was not configured , even after configuring the scanner.

[anandmnair]

I was using 0.9.11 and with scanners it was working fine. but by just changing the version to 0.9.12 , stared getting the exception for "org.reflections.RflectionException: Scanner SubTypeScanner was not configured".

Reflections reflections = new Reflections(new ConfigurationBuilder()
     .setUrls(ClasspathHelper.forPackage("my.project.prefix"))
     .setScanners(new SubTypesScanner(), new TypeAnnotationsScanner()),
     .filterInputsBy(new FilterBuilder().includePackage("my.project.prefix"))
     );

reflections.getSubTypesOf(someClass);  // here it throws exception 

I noticed that, when I add a class which extend some class to the package, this error goes.
Same with FieldAnnotationScanner , or any other scanner.

To try , please provide an invalid package for reflection creation, you will see all these errors coming even after configuring all scanners with reflection

[azell]

Having an enum type in the package path will also fix the problem, as it will force SubTypesScanner to be invoked.

[aheritier]

Same problem for me. Not sure if it's a regression of if I should adapt some code

[azell]

Think removing store.getOrCreate method is the culprit.

[koppor]

Same issue for ResourcesScanner (e.g., example from
https://github.com/ronmamo/reflections/blob/gh-pages/UseCases.md#find-resources-in-your-classpath)

Or

    Reflections reflections = new Reflections(new ResourcesScanner());
    var resources = reflections.getResources(Pattern.compile(".*pom\\.xml"));

Exception in thread "main" org.reflections.ReflectionsException: Scanner ResourcesScanner was not configured

Does not happen with 0.9.11.

[chia7712]

Think removing store.getOrCreate method is the culprit.

+1

    public Reflections(final Configuration configuration) {
        this.configuration = configuration;
        store = new Store(configuration);

        if (configuration.getScanners() != null && !configuration.getScanners().isEmpty()) {
            //inject to scanners
            for (Scanner scanner : configuration.getScanners()) {
                scanner.setConfiguration(configuration);
                scanner.setStore(store.getOrCreate(scanner.getClass().getSimpleName())); // this line
            }

            scan();

            if (configuration.shouldExpandSuperTypes()) {
                expandSuperTypes();
            }
        }
    }

In 0.9.11, the constructor adds collection of all configured scanners to Store before does scan classes. By contrast, 0.9.12 create collection of all configured scanners only if it does scan something successfully. Personally, the error "was not configured" happening in 0.9.12 is a litter weird since the scanner is indeed "configured".

Could we keep the behavior of 0.9.11 (pre-create collection for all configured scanners) to fix this issue ?

[tmortagne]

Same issue here with ResourcesScanner.

Works fine when resource are found but crashing when there is nothing matching the configuration.
Looks like when no resource is found matching the configuration the corresponding map is null instead of being empty which make Store#get(String) think (wrongly) that this scanner was not even configured.

[GodLiang]

I also have this problem.I wan to change another lib.

[porunov]

We just switched to https://github.com/aschoerk/reflections8 (version 0.11.7). Even so it says that it is obsolete after reflections 0.9.12 release, they don't have this bug.
The fix to this issue is provided here: #278 but it wasn't reviewed / merged by repository maintainers.

[tr7zw]

What's the status here? This is a breaking issue that's been open for 5-6 months now, and the pr to fix it got closed without an update?

[TanVD]

Any updates? It is really strange that PR with fix of a problem was closed even without a comment.

[mfvanek]

I've faced with the same bug. Migrated to reflections8

[dano]

I haven't tested it to confirm, but it looks like @ronmamo might have fixed this via #275 on April 26th, the same day the PR that someone provided here was closed without comment.

[AntonOyung]

I upgraded 2 days ago from 0.9.11 to 0.9.12 and I am still seeing this issue

[dano]

Just to clarify my previous comment - you'd have to be using 0.9.13-SNAPSHOT to have the commit I think may have fixed it.

[AntonOyung]

How can I get 0.9.13-SNAPSHOT?

[dano]

@AntonOyung I think you'll have to build it from source yourself. It doesn't look like SNAPSHOT builds get pushed to a maven repository.

[xresch]

I ran into the same issue when migrating from JDK8 to JDK11.
For me the issue didn't occur anymore when I removed the configuration builder and just instantiated the Reflections class like below.
This way works for me for JDK 8, 11 and 13 and with reflection version 0.9.12.

//-------------------------------------------
// Old instantiation that throws an error with 
// reflections 0.9.12 and JDK 11 or higher

//       Reflections reflections = new Reflections(new ConfigurationBuilder()
//            //.filterInputsBy(new FilterBuilder().exclude(FilterBuilder.prefix("com.xresch.cfw.")))
//            .filterInputsBy(new FilterBuilder().exclude(FilterBuilder.prefix("java.")))
//            .setUrls(ClasspathHelper.forClassLoader())
//            //.setScanners(new SubTypesScanner(), new TypeAnnotationsScanner())
//       );
	
//-------------------------------------------
// New instantiation that works with 
// Reflections 0.9.12 and JDK8 or higher
// scans all classes	
Reflections reflections = new Reflections("");

//-------------------------------------------
// No changes here
Set<Class<?>> types = reflections.getTypesAnnotatedWith(CFWExtensionApplication.class);

for(Class<?> clazz : types) {
   if(CFWAppInterface.class.isAssignableFrom(clazz)) {
	   new CFWLog(logger).method("loadExtentionApplication").info("Load CFW Extension Application:"+clazz.getName());
	   
	  try {
		CFWAppInterface instance = (CFWAppInterface)clazz.newInstance();
		return instance;
	} catch (InstantiationException | IllegalAccessException e) {
		new CFWLog(logger).method("loadExtentionApplication").severe("Error loading CFW Extension Application:"+clazz.getName(), e);
	}
   }
}

[ronmamo]

apologize for this inconvenience !

scanner was not configured exception - this is a known issue in 0.9.12, a simple workaround is to check if the getStore() contains index for the scanner before querying. next version 0.10 fixes this.

[ronmamo]

fixed on 0.10