When my embedded Tomcat (8.0.39) is starting in my Maven-Eclipse project,
I get these warnings:
WARNING: Failed to scan
[file:/C:/Users/TEUGELINK/.m2/repository/org/apache/xmlgraphics/fop/0.94/commons-io-1.3.1.jar]
from classloader hierarchy
java.io.FileNotFoundException:
C:\Users\TEUGELINK\.m2\repository\org\apache\xmlgraphics\fop\0.94\commons-io-1.3.1.jar
(Het systeem kan het opgegeven bestand niet vinden) // file cannot be
found
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:219)
at java.util.zip.ZipFile.<init>(ZipFile.java:149)
at java.util.jar.JarFile.<init>(JarFile.java:166)
at java.util.jar.JarFile.<init>(JarFile.java:130)
at
org.apache.tomcat.util.scan.JarFileUrlJar.<init>(JarFileUrlJar.java:60)
at
org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:48)
at
org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner.java:334)
at
org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.java:284)
at org.apache.jasper.servlet.TldScanner.scanJars(TldScanner.java:262)
at org.apache.jasper.servlet.TldScanner.scan(TldScanner.java:106)
at
org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:101)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5303)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
What is weird is that it is looking for the commons-io artifact in a
totally wrong repo group. The project was setup by Eclipse's Maven plugin
(import maven project), and commons-io is indeed part of the project's
Maven dependencies, but in the correct location. The correct commons-io is
also scanned, but somehow 30ish of those incorrect permutations of group
and artifact id are also scanned.
Now these are warnings, so no fuss, but still strange?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
