Its something with the extjs-5.1.0.jar if you eliminate that as a dependency, then the startup / scan is near instantaneous.
Wonder if that's a bad jar file?
Or if java's java.util.jar.JarFile has issues with the the extjs-5.1.0.jar?
Out of curiosity, why are you including an 81MB jar file full of META-INF/resources/ provided _javascript_ examples in the classpath of your WAR?
Its not like anything can make use of that as it is.
What I haven't tested is the new servlet 3.1 META-INF/resources/ logic.
That requires us to unpack the JAR files in WEB-INF/lib that have META-INF/resources/ into a temporary directory.
Using command line ...
$ jar -xf extjs-5.1.0.jar
that takes 3 minutes on my machine. (way way too long)
I'm suspicious of that file now.
OK, how about you unpack that jar into your src/main/webapp (stripping the META-INF/resources/ prefixes) during your build instead.
The dependency plugin might be able to handle that (during the generate-resources phase).
Tho the stripping of the prefix might need a secondary step with the assembly plugin (or careful manipulation of the maven-resources-plugin configuration, or <resources> entries)
That will give you the same end result, but without the negative impact of how META-INF/resources/ works during startup