为什么Eclipse认为应用引擎sdk jar是应用程序引擎SDK的目录？ [英] Why does Eclipse consider that the app engine sdk jar is the directory where the app engine SDK is?

问题描述

我有一个在Eclipse中导入的Google App Engine项目。由于某些原因，当我去Eclipse项目属性时，Google App Engine SDK似乎被保存为jar（appengine-api-1.0-sdk-1.4.0.jar）的位置，而不是实际SDK的位置。
如果我修改项目的设置以使用正确的SDK，则新设置不会保存。
因为我无法修改设置，我无法从Eclipse中部署我的应用程序。

解决方案

它是一个maven gae项目？如果是这样，我可以通过在我的项目构建路径的底部移动maven依赖项来取消sdk的位置。如这里所述 http：// googlewebtoolkit .blogspot.com / 2010/08 / how-to-use-google-plugin-for-eclipse.html

在Java Build Path下，选择订单和导出选项卡，并将所有Maven依赖项移动到BOTTOM，否则，GPE将从构建路径上的Maven repo中看到App Engine和GWT SDK，并抱怨它们无效，这是因为GPE期望具体的SDK结构用于启用其他工具。

I have a Google App Engine project imported in Eclipse. For some reason when I go to Eclipse project properties the Google App Engine SDK seems to be saved as the location of the jar (appengine-api-1.0-sdk-1.4.0.jar) instead of the location where the actual SDK is. If I modify the settings of the project to use the correct SDK, the new setting is not saved. Because I can't modify the setting I can't deploy my application from inside Eclipse anymore.

解决方案

Was it a maven gae project? If so, I was able to 'unstick' the sdk location by moving maven dependencies on the bottom of my project build path. As mentioned in here http://googlewebtoolkit.blogspot.com/2010/08/how-to-use-google-plugin-for-eclipse.html

"Under Java Build Path, select the Order and Export tab and move all Maven dependencies to the BOTTOM. Otherwise, GPE will see the App Engine and GWT SDKs from the Maven repo on the build path and complain that they are not valid. This is because GPE expects a specific SDK structure used to enable other tooling."

这篇关于为什么Eclipse认为应用引擎sdk jar是应用程序引擎SDK的目录？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！