UI Acceleo Launcher 项目失败
我按照这个简单的教程http://wiki.eclipse.org/Acceleo/Getting_Started创建一个 UI 启动器...但是当我完成并右键单击我的 uml 模型时，我没有 acceleo 标签“Acceleo Model to Tex”，所以我无法运行该插件...do你知道怎么样有可能吗？ 我使用 eclipse 版本 3.6.1 和 topcased...
I've followed this simple tutorial http://wiki.eclipse.org/Acceleo/Getting_Started to create an UI launcher...but when I finish and I make a right click on my uml model, I don't have the acceleo tag "Acceleo Model to Tex", so I'm unable to run the plugin...do you know how is it possible?
I use th eclipse version 3.6.1 with topcased...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我只能看到两种方法可以让这个弹出菜单不显示。最不可能的是模型的扩展名与“新建 UI 项目”向导中的“模型文件名过滤器”字段（默认情况下为“*.uml”）不匹配。我不认为这是你的情况，但我想无论如何我都会提到它。
我认为您的情况的问题是：本教程并没有真正向不熟悉 Eclipse 插件的人解释如何使用 UI 项目。即：这个新的“UI 项目”是一个 Eclipse 插件。为了显示它提供的菜单，您必须将该项目作为插件部署在 Eclipse 中。这可以通过将项目导出为可部署插件（右键单击 => Export => 可部署插件和片段）或从包含该项目的 Eclipse 生成一个新的 Eclipse 实例（Run => Run配置... => 双击“Eclipse 应用程序”，然后点击“运行”）。
对于正在开发的插件来说，最后一个解决方案是首选，因为它允许您更改插件并再次生成一个新实例，以便显示更改...但是，如果您不打算开发 Eclipse 插件，这可能不是最佳解决方案，因为它迫使您拥有两个工作区：一个用于开发插件，另一个用于测试。您将在其上生成代码的 UML 模型必须位于此“测试”工作区中。
I can see only two ways for this popup menu not to show. The least likely is that the extension of your model does not match the "model file name filter" field from the "new UI project" wizard ("*.uml" by default). I do not think that this is your case, but thought I would mention it anyways.
What I think is the problem in your case is : this tutorial does not really explain to people who are not familiar with Eclipse plugins how to use the UI project. Namely : this new "UI project" is an Eclipse plugin. In order for the menu it contributes to show, you have to deploy the project as a plugin in your Eclipse. This can be done by exporting the project as a deployable plugin (right-click => Export => Deployable plug-ins and fragments) or by spawning a new Eclipse instance from the Eclipse that contains the project (Run => Run Configurations... => double click 'Eclipse Application' then hit "Run").
This last solution is preferred for plugins undergoing development as it allows you to change the plugin and simply spawn a new instance again in order for the changes to show ... however if you do not aim at developping Eclipse plugins, this might not be the best solution as it forces you to have two workspaces : one for the development of the plugin, another for the testing. The UML model on which you will generate code has to be in this "testing" workspace.