SDK1.8.4 did break cloud enpoint generation

[Johan Compagner]

I updated through eclipse to the 1.8.4 release, but then i tried to do the endpoint generation it failed with this exception:

java.lang.NoSuchMethodException: com.google.api.server.spi.tools.CloudClientLibGenerator.generateClientLib(java.lang.String, com.google.api.server.spi.tools.ClientLibGenerator$Language, java.lang.String, java.io.File)

at java.lang.Class.getMethod(Class.java:1655)

at com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createClientLibFromApiConfig(SwarmApiCreator.java:101)

at com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmApiCreator.createSwarmApi(SwarmApiCreator.java:212)

at com.google.gdt.eclipse.appengine.swarm.wizards.helpers.SwarmServiceCreator.create(SwarmServiceCreator.java:475)

at com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction$1.run(GenerateSwarmApiAction.java:84)

at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)

at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)

at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)

at com.google.gdt.eclipse.appengine.swarm.wizards.GenerateSwarmApiAction.run(GenerateSwarmApiAction.java:80)

at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)

at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)

at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)

at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)

at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)

at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)

at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)

at org.eclipse.equinox.launcher.Main.run(Main.java:1450)

at org.eclipse.equinox.launcher.Main.main(Main.java:1426)

i quickly reverted to 1.8.3 and that works fine.

Also in 1.8.4 i suddenly also got another json exception that a @named string param was conflicting (which works fine in 1.8.3)

that names param (so thats in the url) does somehow collide with a name that is nested deep down in the body object (which is a java (json) object)

So the name param would be something like:

"code"

and deep down in the body contents i would also have something like

"object.object2.code"

now it seems that those 2 are the same and conflict with each other?

[Ludovic Champenois]

Which version of the GPE plugin itself are you using? Verify it is the latest: GPE 3.4.0

[Johan Compagner]

then thats the problem, because i am on 3.3 and this morning i did get a googles own notification that there is an update (and that i should call check for updates)

But when i do check for updates in eclipse, eclipse tells me that there are no updates..

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/iHsNIT3BURY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[Antonio Villegas]

I have the same problem with 1.8.4. What should I do? How can I downgrade to 1.8.3?

[Vinny P]

On Mon, Sep 9, 2013 at 1:29 AM, Antonio Villegas <lote...@gmail.com> wrote:

I have the same problem with 1.8.4. What should I do? How can I downgrade to 1.8.3?

Download the old version from the Maven repository: http://search.maven.org/#browse%7C1910764113  

 

 

-----------------

-Vinny P

Technology & Media Advisor

Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

[Johan Compagner]

now that 1.8.5 is out i throught lets try it again

But at first the same problem again.

But then i rechecked what GPE i had installed and yes it was 3.3.x 

Check for updates didn't really update that, but then i did go through -> install new software

with the 4.3 url (that i already was using for a long time) and there i did see the 3.4.x version 

When i selected that to install, Eclipse said at first that it can't really install it because of conflicts, but after while eclipse came to the conclusion that it could uninstall 3.3 and install 3.4 

After that was being installed and after a restart it seemed to work fine.

But the problem is that 3.3 is not updated somehow to 3.4 (i did get updates but i guess not really 3.4)

So this could be a problem of many others also, which are coming from an older install and are constantly just upgrading..