Classpath issues about gradle-appengine-plugin HOT 9 CLOSED

I tried to run your app locally and it worked. Is this error from running on appengine? Is the $APPENGINE_HOME on your machine pointing to the same version of appengine as defined in your build-script?

from gradle-appengine-plugin.

Did you try to upload data/orders1.xml?

And it worked?

I get the same error locally and on appengine.

I have not any APPENGINE_HOME set at all ...

2013/11/8 nilsmagnus [email protected]

I tried to run your app locally and it worked. Is this error from running
on appengine? Is the $APPENGINE_HOME on your machine pointing to the same
version of appengine as defined in your build-script?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-28048232
.

[Hem: 08-715 59 57, Mobil: 0708-52 62 90]
Allévägen 2A, 132 42 Saltsjö-Boo

from gradle-appengine-plugin.

Sorry, tried with the submission of the order xml and got the same error. It seems like the classpath issues in the plugin, indeed.

from gradle-appengine-plugin.

Thx for verifying that!

2013/11/8 nilsmagnus [email protected]

Sorry, tried with the submission of the order xml and got the same error.
It seems like the classpath issues in the plugin, indeed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/18#issuecomment-28057159
.

[Hem: 08-715 59 57, Mobil: 0708-52 62 90]
Allévägen 2A, 132 42 Saltsjö-Boo

from gradle-appengine-plugin.

Comments by anyone please!

from gradle-appengine-plugin.

So, the war&explodeApp tasks do the work to copy library depedencies from gradle's cache into the war directory. Is there a reason you have a custom war directory and are not using the "src/main/webapp" area for your meta data? The appengine devserver isn't using gradle to resolve it's dependencies, it just looks in WEB-INF/lib. If you do copy all your dependencies into there I believe it would work.

from gradle-appengine-plugin.

I just made a try to move things into src/main/webapp but the problem is still there.

Please take a minute someone and look whats wrong inside this minimal test project.

See https://github.com/oakstair/gradle-gae-plugin-tryout

from gradle-appengine-plugin.

Yesterday I made a new try with https://github.com/oakstair/gradle-gae-plugin-tryout

First I got the same problem but then suddenly it started to work. Really frustrating.

I laborated with updating my jdk 1.7 to latest version perhaps I cant see what was change that was fixing the classpath problem when uploading the orders1.xml file.

I have commited my changes to gradle-gae-plugin-tryout

One irritating message is "Class JavaLaunchHelper is implemented in both ..."

€ gradle appRun
:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:processResources UP-TO-DATE
:classes
:war
:appengineExplodeApp
:appengineRun
Executing [/Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java, -Xdebug, -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8889, -Xmx1024m, -XX:MaxPermSize=512m, -XstartOnFirstThread, -javaagent:/Users/gunnar/dev/appengine-java-sdk-1.9.19/lib/agent/appengine-agent.jar, -Xbootclasspath/p:/Users/gunnar/dev/appengine-java-sdk-1.9.19/lib/override/appengine-dev-jdk-overrides.jar, -classpath, /Users/gunnar/dev/gradle-2.3/lib/gradle-launcher-2.3.jar:/Users/gunnar/dev/appengine-java-sdk-1.9.19/lib/appengine-tools-api.jar, com.google.appengine.tools.development.DevAppServerMain, --property=kickstart.user.dir=/Users/gunnar/git/gradle-gae-plugin-tryout, --port=8888, --address=localhost, --allow_remote_shutdown, /Users/gunnar/git/gradle-gae-plugin-tryout/build/exploded-app]
objc[5985]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/bin/java and /Library/Java/JavaVirtualMachines/jdk1.7.0_80.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.

But since it work this issue may be closed I guess even do I don't know what fixed the problem.

from gradle-appengine-plugin.

perhaps your answer is here? http://stackoverflow.com/questions/20794751/class-javalaunchhelper-is-implemented-in-both-one-of-the-two-will-be-used-whic

from gradle-appengine-plugin.