java - WARNING: Failed to scan <>.jar from classloader hierarchy. FileNotFoundException -


so have project: https://github.com/leejjon/blindpool

when try release app engine google app engine deployment run configuration in intellij works , deploys fine too.

but lot of warnings (this one):

deploying '[2017-07-27 23:15:04] maven build: blindpool. project: blindepoule. version: 6'... created temporary staging directory: c:\users\leejjon\appdata\local\temp\gae-staging-blindepoule684 reading application configuration data... jul 27, 2017 11:15:06 pm com.google.apphosting.utils.config.indexesxmlreader readconfigxml info: processed c:\users\leejjon\ideaprojects\blindpool\target\blindpool-1.0-snapshot\web-inf\appengine-generated\datastore-indexes-auto.xml   beginning interaction module default... 0% scanning jsp files. 0% compiling jsp files. jul 27, 2017 11:15:07 pm org.apache.tomcat.util.scan.standardjarscanner scan warning: failed scan [file:/c:/users/leejjon/appdata/local/google/cloud%2520sdk/google-cloud-sdk/platform/google_appengine/google/appengine/tools/java/lib/impl/appengine-api-labs.jar] classloader hierarchy java.io.filenotfoundexception: c:\users\leejjon\appdata\local\google\cloud%20sdk\google-cloud-sdk\platform\google_appengine\google\appengine\tools\java\lib\impl\appengine-api-labs.jar (the system cannot find path specified) @ java.util.zip.zipfile.open(native method) @ java.util.zip.zipfile.<init>(zipfile.java:219) @ java.util.zip.zipfile.<init>(zipfile.java:149) @ java.util.jar.jarfile.<init>(jarfile.java:166) @ java.util.jar.jarfile.<init>(jarfile.java:103) @ sun.net.www.protocol.jar.urljarfile.<init>(urljarfile.java:93) @ sun.net.www.protocol.jar.urljarfile.getjarfile(urljarfile.java:69) @ sun.net.www.protocol.jar.jarfilefactory.get(jarfilefactory.java:109) @ sun.net.www.protocol.jar.jarurlconnection.connect(jarurlconnection.java:122) @ sun.net.www.protocol.jar.jarurlconnection.getjarfile(jarurlconnection.java:89) @ org.apache.tomcat.util.scan.jarfileurljar.<init>(jarfileurljar.java:47) @ org.apache.tomcat.util.scan.jarfactory.newinstance(jarfactory.java:36) @ org.apache.jasper.servlet.tldscanner$tldscannercallback.scan(tldscanner.java:301) @ org.apache.tomcat.util.scan.standardjarscanner.process(standardjarscanner.java:313) @ org.apache.tomcat.util.scan.standardjarscanner.scan(standardjarscanner.java:245) @ org.apache.jasper.servlet.tldscanner.scanjars(tldscanner.java:262) @ org.apache.jasper.servlet.tldscanner.scan(tldscanner.java:106) @ org.apache.jasper.jspc.initservletcontext(jspc.java:1535) @ org.apache.jasper.jspc.execute(jspc.java:1378) @ com.google.appengine.tools.admin.localjspc.main(localjspc.java:33) 

then same exception occurs lot of other jars javax.annotation-api-1.2.jar, asm-commons-5.0.1.jar, asm-5.0.1.jar, javax.transaction-api-1.2.jar, javax.mail.glassfish-1.4.1.v201005082020.jar, org.apache.taglibs.taglibs-standard-spec-1.2.5.jar, org.apache.taglibs.taglibs-standard-impl-1.2.5.jar , 30 others.

but deployment continues:

jul 27, 2017 11:15:08 pm org.apache.jasper.servlet.tldscanner scanjars info: @ least 1 jar scanned tlds yet contained no tlds. enable debug logging logger complete list of jars scanned no tlds found in them. skipping unneeded jars during scanning can improve startup time , jsp compilation time. jul 27, 2017 11:15:08 pm org.apache.jasper.jspc processfile info: built file: \index.jsp 2017-07-27 23:15:10.115:info::main: logging initialized @175ms 2017-07-27 23:15:11.051:info:oeja.annotationconfiguration:main: scanning elapsed time=501ms 0% generated git repository information file. success. temporary staging module default directory left in c:\users\leejjon\appdata\local\temp\gae-staging-blindepoule684 services deploy:  descriptor:      [c:\users\leejjon\appdata\local\temp\gae-staging-blindepoule684\app.yaml] source:          [c:\users\leejjon\appdata\local\temp\gae-staging-blindepoule684] target project:  [blindepoule] target service:  [default] target version:  [6] target url:      [https://blindepoule.appspot.com]   beginning deployment of service [default]... files skipped. pass `--verbosity=info` see ones. may view gcloud log file, found @ [c:\users\leejjon\appdata\roaming\gcloud\logs\2017.07.27\23.15.12.062000.log]. #============================================================# #= uploading 4 files google cloud storage                =# #============================================================# file upload done. updating service [default]... ..............done. updating service [default]... .waiting operation [apps/blindepoule/operations/5106d598-f760-4079-a358-4b2148c622cf] complete... ..done. done. deployed service [default] [https://blindepoule.appspot.com]  can stream logs command line running:   $ gcloud app logs tail -s default  view application in web browser run:   $ gcloud app browse '[2017-07-27 23:15:04] maven build: blindpool. project: blindepoule. version: 6' has been deployed successfully. 

as can see finishes fine, should worry getting rid of warnings?

update: found out google wants move use cloud tools appengine maven plugin: https://cloud.google.com/appengine/docs/standard/java/tools/migrate-maven

if use recommended setting , run gcloud appengine:deploy exact same error got in intellij before. using old appengine maven plugin works goes against google recommends.

it seems need manage correctly versions in pom.xml. plugins not accessible more under specified version.

i've tried:

    <plugins>     ...         <plugin>             <groupid>com.google.appengine</groupid>             <artifactid>appengine-maven-plugin</artifactid>             <!--<version>${appengine.target.version}</version>-->             <version>1.8.3</version>             <configuration>             </configuration>         </plugin>         <plugin>             <groupid>org.eclipse.jetty</groupid>             <artifactid>jetty-maven-plugin</artifactid>             <!--<version>${jetty.maven.plugin}</version>-->             <version>9.4.0.v20161208</version>         </plugin>     </plugins> 

and i've started server without problem.


plugin , dependency version can different (because of shifted releases or cleaning repositories). can use plugin versions i've specified or play changing ones more if want use same version dependency , plugin.


connected target vm, address: '127.0.0.1:64711', transport: 'socket' jul 28, 2017 1:06:54 com.google.apphosting.utils.jetty.jettylogger info info: logging jettylogger(null) via com.google.apphosting.utils.jetty.jettylogger connected server jul 27, 2017 10:06:54 pm com.google.apphosting.utils.jetty.jettylogger info info: jetty-6.1.x jul 27, 2017 10:06:55 pm com.google.apphosting.utils.jetty.jettylogger info info: started selectchannelconnector@localhost:8080 jul 27, 2017 10:06:55 pm com.google.appengine.tools.development.abstractmodule startup info: module instance default running @ http://localhost:8080/ jul 27, 2017 10:06:55 pm com.google.appengine.tools.development.abstractmodule startup info: admin console running @ http://localhost:8080/_ah/admin jul 28, 2017 1:06:55 com.google.appengine.tools.development.devappserverimpl dostart info: dev app server running 

Comments

Popular posts from this blog

php - Vagrant up error - Uncaught Reflection Exception: Class DOMDocument does not exist -

vue.js - Create hooks for automated testing -

Add new key value to json node in java -