Match Processor Exception

[GedMarc]

Hey Luke!

Sooo, i'm guessing I need to expose something for a process exception?

JDK 10.0.1

Exception creating Injector : Multiple exceptions thrown of type: java.lang.NullPointerException. To see individual exceptions, call MatchProcessorException#getExceptions(), or call FastClasspathScanner#verbose() before FastClasspathScanner#scan().io.github.lukehutch.fastclasspathscanner.MatchProcessorException: Multiple exceptions thrown of type: java.lang.NullPointerException. To see individual exceptions, call MatchProcessorException#getExceptions(), or call FastClasspathScanner#verbose() before FastClasspathScanner#scan().
at io.github.lukehutch.fastclasspathscanner@3.1.10/io.github.lukehutch.fastclasspathscanner.MatchProcessorException.newInstance(MatchProcessorException.java:92)

[lukehutch]

Hi @GedMarc -- did you try calling the method this exception suggests? That will let you get all the individual exceptions, then you can call their printStackTrace() method to see what happened and where.

[GedMarc]

mmm

Caused by: java.lang.NullPointerException
at io.github.lukehutch.fastclasspathscanner@3.1.10/io.github.lukehutch.fastclasspathscanner.scanner.Scanner.call(Scanner.java:359)
at io.github.lukehutch.fastclasspathscanner@3.1.10/io.github.lukehutch.fastclasspathscanner.scanner.Scanner.call(Scanner.java:58)
at java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)

• [SEVERE]

[GedMarc]

scanner.verbose(true);
	scanner.createClassLoaderForMatchingClasses();

	registerScanQuickFiles(scanner);
	scanner.suppressMatchProcessorExceptions(false);
	try
	{
		scanResult = scanner.scan(getThreadCount());
	}
	catch (MatchProcessorException mpe)
	{
		System.out.println(mpe.getExceptions());
	}

[lukehutch]

Thanks, modular scanning has not yet been widely tested, so please report any other issues you find. Fixed in 3.1.12.

[GedMarc]

It's happening on this error :) thanks I'll give it a try now

[lukehutch]

Yes, I hadn't tested verbose logging with a modular classpath recently. Module classpath elements don't have an associated File in FCS (i.e. the value is null if there's a module involved, hence the NPE), since most of the URLs for modules are not valid URLs, they are of the form jrt:/module.name. I'm actually surprised that this module of yours does in fact have a valid file:/ URL, so I'll probably add that to the log as well.