Eclipse PDE - 插件、功能和产品版本控制
我对在相当大的 Eclipse 工作区中升级依赖插件、功能和产品的版本号的过程感到非常困惑。
我对现有插件中的 java 代码进行了 API 更改，因此需要增加版本标识符的 Major 部分。该插件充当给定功能的依赖项，该功能稍后会包含在产品中。从 http://wiki.eclipse.org/Version_Numbering 的文档中，我理解（大部分）何时应在包含插件本身上增加适当的数量。
但是，插件上的这个主要版本号更改将如何影响依赖的“下线”项目（例如功能、产品）？
例如，假设我们有如下典型的“Hello World”设置：
插件：com.example.helloworld，版本 1.0.0
功能：com.example.helloworld.feature，版本 1.0.0
产品：com.example.helloworld.product，版本 1.0.0
如果我要在插件中进行 API 更改，则需要进行版本更新2.0.0 的那个。那么该功能的版本是多少，1.1.0？同样的问题也适用于产品级别（例如，如果功能是 1.1.0 或 2.0.0，产品版本号是多少）？
我确信这是一个新手问题，所以我为浪费任何人的时间和精力而道歉。我已经搜索过此类内容，但我找到的只是展示如何首次开发插件、功能、产品和更新站点的示例。与我的搜索相关的唯一其他内容是开发功能补丁，并且没有像我希望的那样触及版本控制方面。我（第一次）进入 Eclipse RCP / PDE 环境时遇到困难，需要学习进行此类版本控制更新的正确方法和/或最佳实践，以及如何在工作区中的其他相关项目中最好地反映这一点。
I am having much confusion over the process of upgrading version numbers in dependent plug-ins, features, and products in a fairly large eclipse workspace.
I have made API changes to java code residing in an existing plug-in and thus requires an increase of the Major part of the version identifier. This plug-in serves as a dependency to a given feature, where the feature is later included in a product. From the documentation at http://wiki.eclipse.org/Version_Numbering, I understand (for the most part) when the proper number should be increased on the containing plug-in itself.
However, how would this Major version number change on the plug-in affect dependent, "down-the-line" items (e.g., features, products)?
For example, assume we have the typical "Hello World" setup as follows:
Plug-in: com.example.helloworld, version 1.0.0
Feature: com.example.helloworld.feature, version 1.0.0
Product: com.example.helloworld.product, version 1.0.0
If I were to make an API change in the plug-in, this would require a version update to be that of 2.0.0. What would then be the version of the feature, 1.1.0? The same question can be applied for the product level as well (e.g., if the feature is 1.1.0 OR 2.0.0, what is the product version number)?
I'm sure this is quite the newbie question so I apologize for wasting anyone's time and effort. I have searched for this type of content but all I am finding is are examples showing how to develop a plug-in, feature, product, and update site for the first time. The only other content related to my search has been developing feature patches and have not touched on the versioning aspect as much as I would prefer. I am having difficulty coming into (for the first time) an Eclipse RCP / PDE environment and need to learn the proper way and / or best practices for making such versioning updates and how to best reflect this throughout other dependent projects in the workspace.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您想对功能和产品应用相同的版本控制系统，那么当其中一个插件变为 2.0.0 时，您可以将功能和产品设置为 2.0.0。这会告诉任何使用你的功能或产品的人，其中某处有一个重大的 API 更改。
另一方面，不需要应用相同的版本控制约定。您可以按照该约定对捆绑包进行版本控制，以正确传达您的 API 更改，然后转身对产品/功能使用更适合营销的版本。请记住，用户将看到的产品/功能版本多于单个捆绑版本。
我已经看到这两种方式都有效地完成了。这实际上没有正确或错误的方法。
If you would like to apply the same versioning systems to feature and product, then you would set feature and product to 2.0.0 when one of the plugins go to 2.0.0. That would communicate to whoever is consuming your feature or product that there is a breaking API change inside it somewhere.
On the other hand, there is no requirement to apply the same versioning convention. You can version your bundles following that convention to properly communicate your API changes and then turn around and use more marketing-sensible versions for product/feature. Keep in mind that user will see product/feature version more than they will individual bundle version.
I've seen it done both ways effectively. There isn't really a right or wrong way on this.