JAR and GAE Marketplace for Google Apps

When you use the Google-Eclipse plugin to create a new web application project and you select the Add support for inclusion in the Google Apps Marketplace option, the plugin automatically adds the apps-marketplace.jar

file in your classpath.

Does this mean - at any given time, for whatever reason, should ever be associated with your WAR? I ask because it bundles a version of SLF4J which causes JAR hell problems with other dependencies using a different version of SLF4J.

I included it in my WAR because I thought it was necessary, but if its something that is just used by a plugin, or possibly available as some kind of service for GAE apps when they are running in production, this is needed and wanted would remove it as a dependency. Thanks in advance.

+3


source to share


1 answer


This bank is not needed. You can remove it from your build path and your WAR directory. We need to fix the plugin to get rid of this jar.



I have a feeling it was first added to make it easier to access some of the Google APIs from your Marketplace app. It included a bunch of classes for handling OAuth. However, I think all the classes here are mostly deprecated and there are better ways to make these Api calls now.

+3


source







All Articles