运行 RCP 应用程序

发布于 2024-12-27 04:33:56 字数 269 浏览 0 评论 0原文

有很多方法可以运行应用程序。我可以从

  • 创建的产品的plugin.xml概述选项卡
  • (文件->新建->插件开发->产品配置)
  • 手动创建运行配置

我想知道的主要区别是第一个和第二个之间的区别选项,因为它对我来说是最令人困惑的。

对于第二个和第三个选项,我认为通过创建产品配置并第一次运行它,会自动创建继承产品配置选项的新运行配置。创建运行配置后,不再有来自产品配置和链接配置的连接(至少我没有看到)?

There is a bunch of ways to run an application. I could run it from:

  • plugin.xml overview tab
  • from created product (file->New->Plugin development->Product configuration)
  • manually create run configuration

The main difference which I want to know is between the first and the second option as it is the most confusing for me.

For the second the third option I think that by creating product configuration and running it first time new run configuration inheriting product configuration options is automatically created. After run configuration is created there is no more connections from product configuration and link configuration (at least I have not seen one)?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

箜明 2025-01-03 04:33:56
  • 选项 1 - 通过 plugin.xml 运行 - 主要在相关插件使用完整目标平台时使用。除非您明确设置了目标平台,否则这与您正在运行的 IDE 相同。当然,您可以稍后手动限制启动配置所使用的插件集...
  • 选项 2 - 通过产品配置运行 - 当您定义了完整的产品时使用。每次使用此选项时,都会同步底层启动配置以匹配产品配置。当您根据功能定义产品或仅使用已定义目标平台的子集时,这尤其有用。另外,当您希望调试通过产品配置定义的产品时,这很有用...
  • 选项 3 - 通过手动创建的启动配置运行 - 是我尝试避免的一个选项,因为当您更改插件时它经常会变得混乱产品的功能或产品配置...在新产品/应用程序作为初始(基于插件)产品的开发开始时手动维护启动配置可能非常有用配置可以从启动配置生成。
  • Option 1 - run via plugin.xml - is primary used when the plug-in in question uses the complete target platform. Unless you have set the target platform explicitly, this is the same as the IDE you are running. Of cause, you can then later restrict the used set of plug-ins for your launch configuration manually...
  • Option 2 - run via product configuration - is used when you have defined a complete product. Every time you use this option, an underlying launch configuration is synched to match the product configuration. This is especially useful when you have defined you product in terms of features or only use a subset of the defined target platform. Also, this is useful when you wish to debug a product that is defined via a product configuration...
  • Option 3 - run via manual created launch configuration - is an option I try to avoid as it often gets confusing when you change plug-ins, features or product configurations for the product... It can be very useful to maintain a launch configuration manually in the beginning of development of a new product/application as the initial (plug-in based) product configuration can be generated from a launch configuration.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文