Google plugin in MyEclipse 9 - Unable to sign in

[Martin]

Hiya,

I've got something very weird happening using the Google plugin with
MyEclipse 9, but I am out of ideas as to what it could be. I've
developed and deployed Java websites to GAE, using older versions of
the Google plugin, but with the latest one, I seem unable to do
anything. I simply cannot click on the "sign in to Google" button, and
have anything happen. I click it, and zero, zilch, nada, nothing
happens at all. I can right-click it, and get prompted for "Icon only"
or "Sign out on exit", but cannot actually sign in.

I've tried multiple installs on multiple computers, with both old and
new workspaces. I've tried it with Google web projects selected and
open, I've tried it with non-Google projects, and I've tried it with
an empty workspace.

Despite various searches over a few weeks, I've found no other posts
about this problem, so I've figured that it's either (a) something
fundamentally wrong with my setup or (b) something fundamentally dumb
that I'm doing.

Can anyone please point me in the right direction for fixing this?

Yours hopefully and sheepishly,

Martin

[Martin]

Sorry to bump, but can anyone please help? I have genuinely tried
everything and searched everywhere, but for whatever reason am unable
to find an answer!

[Roland Schweitzer]

I just ran into this problem myself.

Here's the uncaught exception that gets thrown when you try to login or deploy to App Engine:

!ENTRY org.eclipse.ui 4 0 2011-07-14 10:40:51.555

!MESSAGE Unhandled event loop exception

!STACK 0

java.lang.LinkageError: loader constraint violation: when resolving method "com.google.gdt.eclipse.login.LoginCallbackServer.addServlet(Ljava/lang/String;Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, com/google/gdt/eclipse/login/LoginCallbackServer, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, com/google/gdt/eclipse/login/LoginCallbackServer, have different Class objects for the type javax/servlet/Servlet used in the signature

at com.google.gdt.eclipse.login.LoginCallbackServer.<init>(LoginCallbackServer.java:137)

at com.google.gdt.eclipse.login.GoogleLogin.logIn(GoogleLogin.java:403)

at com.google.appengine.eclipse.core.deploy.ui.DeployProjectHandler.execute(DeployProjectHandler.java:51)

at com.google.appengine.eclipse.core.deploy.ui.DeployProjectAction.run(DeployProjectAction.java:13)

I did my best to figure out how to resolve the conflict by loading various versions of the servlet-api.jar ahead of the version in the App Engine SDK, but no joy.  I don't know who could best resolve this the Genuitec or the Google plugin team, but I couldn't figure it out in the time I devoted to it.

I finally did a fresh install of the basic (not MyEclipse) Eclipse Java (time to try Indigo anyway) and added the Google plugins and SDKs and deployed to App Engine from there.  I now have an Eclipse with just the Android plugins, an Eclipse with App Engine and GWT for App Engine projects and MyEclipse which I use for web projects with GWT (but not deployed on App Engine).  It's a bit of a bother, but my experience is that there are always conflicts with Eclipse that can be minimized with this sort of segregation.

Not the answer you were looking for, but it's how I got it working.

Roland

[Martin]

Thank you ... I appreciate your posting. I will do that. I've been
muddling by with various snippets here and there, but it's ultimately
failing to do what I need, so your suggestion sounds sensible.


On Jul 14, 5:18 pm, Roland Schweitzer <roland.schweit...@gmail.com>
wrote:

> I just ran into this problem myself.
>
> Here's the uncaught exception that gets thrown when you try to login or
> deploy to App Engine:
>
> !ENTRY org.eclipse.ui 4 0 2011-07-14 10:40:51.555
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method

> "com.google.gdt.eclipse.login.LoginCallbackServer.addServlet(Ljava/lang/Str ing;Ljavax/servlet/Servlet;)V"

> the class loader (instance of
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current
> class, com/google/gdt/eclipse/login/LoginCallbackServer, and the class
> loader (instance of
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved
> class, com/google/gdt/eclipse/login/LoginCallbackServer, have different
> Class objects for the type javax/servlet/Servlet used in the signature
> at

> com.google.gdt.eclipse.login.LoginCallbackServer.<init>(LoginCallbackServer .java:137)

> at com.google.gdt.eclipse.login.GoogleLogin.logIn(GoogleLogin.java:403)
> at
> com.google.appengine.eclipse.core.deploy.ui.DeployProjectHandler.execute(De ployProjectHandler.java:51)
> at

> com.google.appengine.eclipse.core.deploy.ui.DeployProjectAction.run(DeployP rojectAction.java:13)

[Bo Eriksson]

Similar problem using Springsource STS and/or reg eclipse 3.7. Nothing whatsoever happends when clicking the google plugin in left corner (or the deploy to appengine). Had it working just after installation on STS but unable to login now so I suspect there is a troll in my environment..

[Richard Wagenknecht]

I get the exact same behavior. Fresh install of STS 3.7. Deploy does nothing nor can I sign in to google.

[Stuart Gielen]

And another victim here! I was logged in fine, but after logging out I can no longer log back in.

Same result: clicking on 'Sign in to Google' button does nothing.

Can anyway help us out with this issue? It's a real show stopper.