Eclipse PDE - Plugin, Feature, and Product Version

Question

I get a lot of confusion when updating version numbers in dependent plugins, functions, and products in a rather large eclipse workspace.

I made API changes to the Java code found in the existing plug-in, and therefore requires an increase in the Major part of the version identifier. This plug-in serves as a dependency on this function, in which the function is later included in the product. From the documentation at http://wiki.eclipse.org/Version_Numbering, I understand (for the most part) when the corresponding amount should be increased on the containing plug-in itself.

However, how will this Major number change to down-line elements (such as functions, products) dependent on the connected device?

For example, suppose we have a typical Hello World setting:

com.example.helloworld, version 1.0.0 : com.example.helloworld, version 1.0.0
Function: com.example.helloworld.feature, version 1.0.0
Product: com.example.helloworld.product, version 1.0.0

If I needed to change the API in the plug-in, this would require an update of version 2.0.0. What version 1.1.0 version? The same question can be applied to the product level (for example, if the function is 1.1.0 or 2.0.0, then what is the version number of the product)?

I am sure that this is quite a newbie, so I apologize for wasting time and effort. I searched for this type of content, but all I find are examples showing how to develop a plugin site, function, product, and update for the first time. The only other content related to my search was to develop feature patches and not affect the aspect of the version, as far as I would prefer. I am having difficulty entering (for the first time) into the Eclipse RCP / PDE environment and I need to learn the proper way and / or best practices for creating such version updates and how best to reflect this in all other dependent projects in the workspace.

Answer 1

If you want to apply the same version control systems to functions and products, then you will set the function and product to 2.0.0 if one of the plugins goes to 2.0.0. This will inform those who consume your feature or product that somewhere in it there is a violation of the API.

On the other hand, there is no requirement to apply the same version convention. You can update your packages in accordance with this agreement in order to properly report API changes, and then turn around and use more marketing ideas for the product / function. Keep in mind that the user will see the product / function version more than the individual package version.

I saw how this was done in both directions. Actually there is no right or wrong way.