search

vcgato29 / google-plugin-for-eclipse

Automatically exported from code.google.com/p/google-plugin-for-eclipse
Eclipse Public License 1.0
0 stars 0 forks source link

Extending com.google.gdt.eclipse.login.oauthClientProvider #273

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
A plugin that extends com.google.gdt.eclipse.login.oauthClientProvider does not 
necessarily get used.  The behavior is random due to extension registry order.

The method   initializeOauthClientInfo in GoogleLogin  pick the first provider 
with non-empty clientid/secret.  The builtin OauthClientInfo can takes 
precendence over contributed ones.

What is the recommended method for having a provider to get used?

Original issue reported on code.google.com by naci....@eteration.com on 16 Mar 2014 at 2:10

GoogleCodeExporter commented 9 years ago 
We were not intending on having anyone extend/re-use this plugin. Could you 
elaborate more on your use-case?

Original comment by rdayal@google.com on 12 May 2014 at 6:32

GoogleCodeExporter commented 9 years ago

Original comment by rdayal@google.com on 12 May 2014 at 6:32

GoogleCodeExporter commented 9 years ago 
I am building a set of eclipse plugins for developing glassware that uses glass 
APIs. 

https://github.com/eteration/glassmaker

Plugins allow "preview on glass" feature that requests permission from the 
glass developer to push data to the glass.  The requires developer to use their 
own CLIENT secret and CLIENTID, which they can provide via eclpise preferences.

https://github.com/eteration/glassmaker/blob/master/org.glassmaker.eclipse/org.g
lassmaker.ui.editor/src/main/java/org/glassmaker/login/GlassmakerClientProvider.
java

Original comment by naci....@eteration.com on 13 May 2014 at 8:56