如何使用Eclipse GAE插件部署包含GWT模块的GWT项目,无需入口点? [英] How to deploy GWT Project containing GWT modules without entry points with Eclipse GAE plugin?
问题描述
当我选择通过部署App Engine项目选项将我的项目部署到Google App Engine时,所有模块都将被编译,此过程被困在库模块上,因为它们没有定义入口点。
有没有办法解决这个问题?我现在通过将Dummy.java文件添加到实现EntryPoint的库中并在其中具有一个空的onModuleLoad来修复它。
p>您可以告诉GWT哪个模块有一个入口点。右键单击项目的图标,选择Google> Web Toolkit设置...,然后从入口点模块列表中删除您的库模块。
此更改将持续存在,并将影响所有编译操作,包括部署到GAE。您从GWT编译项目中选择的选项是暂时的,只能进行一次编译。
这应该告诉部署应用程序引擎项目操作来停止尝试编译您的图书馆模块。
I have a GWT Project containing some GWT modules that I would like to have NO entry point, functioning as libraries for other modules WITH entry points.
The GWT 'entry point' modules compile fine with the "GWT Compile Project" option in Eclipse if I choose not to compile the GWT 'library' modules with them. They also run fine.
When I choose to deploy my project to the Google App Engine with the "Deploy App Engine Project" option, all modules will get compiled and this process gets stuck on the 'library' modules, since they have no entry point defined.
Is there a way to get around this? I now 'fixed' it by adding a Dummy.java file to the libraries that implement EntryPoint and have an empty onModuleLoad in them.
You can tell GWT which modules have an entry point. Right-click on the icon for the project, choose Google > Web Toolkit Settings..., and remove your library module from the list of "Entry Point Modules."
This change is persistent and will affect all of your compiling actions, including deploying to GAE. The options you choose from "GWT Compile Project" are transient and only last for one compile.
This should tell the "deploy app engine project" action to stop trying to compile your library modules.
这篇关于如何使用Eclipse GAE插件部署包含GWT模块的GWT项目,无需入口点?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!