Scan with Scala library in classpath gives error about different superclasses

See the attached fast-classpath-scanner-scala.tar.gz file containing a Gradle project which runs a test attempting to scan with the Scala library version 2.12.4 in the classpath.

The archive includes a verbose.log file from my local run (on a Mac). The exception message is:

Caused by: java.lang.IllegalArgumentException: A class and its auxiliary class have different superclasses: class extends scala.collection.generic.SeqFactory<scala.collection.immutable.Stack> implements scala.Serializable ; <A> class extends scala.collection.AbstractSeq<A> implements scala.collection.immutable.LinearSeq<A>, scala.collection.LinearSeqOptimized<A, scala.collection.immutable.Stack<A>>, scala.Serializable

You should be able to run yourself using:

tar xvfz fast-classpath-scanner-scala.tar.gz
cd fast-classpath-scanner-scala
./gradlew build

The test sends System.out/System.err to the verbose.log file.

For now, I’ll try to work around the issue by determining how to exclude certain packages or files from scanning.

[lukehutch]

@ryan-gustafson @pshirshov this is fixed in 2.19.0.

You will now get pkg.Class for a base class in Scala, pkg.Class$ for a companion object, and pkg.Class$class for a trait methods class (i.e. these are no longer merged into pkg.Class).

[lukehutch]

@ryan-gustafson I just pushed out version 2.20.1, with support for explicitly blacklisting classpath elements based on a string match criterion:

https://github.com/lukehutch/fast-classpath-scanner/releases/tag/fast-classpath-scanner-2.20.1

This will work better than the code snippet I gave in #190, since it applies the filtering before extracting jars-within-jars (in the case that you have classpath elements like path/to/jar1.jar!/BOOT-INF/lib/jar2.jar).

(However, hopefully you don’t need to skip directories now that Scala scanning is fixed.)