CODEWITHSUNDEEP
eclipseeclipse-plugin
ilke Muhtaroglu
ilke Muhtaroglu

Reputation: 137

How to automate Eclipse Plugin versioning?

We have 20 plugin in our project. After each build we have to update our plugin version from ´Manifest.mf´ file.

Bundle-Version: 1.0.0.qualifier

For example after an update I have to manually update this line and give a new number? How can I automate this for 20 plug-ins?

I see that at Eclipse plug-ins there is 3.3.1.v20150403-1352. How do they achieve this? How we can have such a versioning system. Such as major version, then minor version then date of the build and the hour.

Any ideas are welcome.

At the moment we thought to write a plugin view where we can manually update these lines by entering from a main view. But even what we thought as a solution is not easy. There should be a tidy way to do the versioning, but how?

Is it done through PDE API & Build?

I found these links:

Here it states:

"In Eclipse, version numbers are composed of four (4) segments: 3 integers and a string respectively named major.minor.service.qualifier."

This is given automatically when the plugin is created and how can I have Eclipse PDE update this automatically when I change a code in plugin?

In the IBM link it says that Eclipse gives you error when you need to change the @since tag and manifest file. Any help is appreciated regarding this topic.

Upvotes: 2

Views: 530

Answers (1)

greg-449
greg-449

Reputation: 111142

The major, minor and micro values are generally just set 'by hand'.

When the qualifier value is specified as 'qualifier' it is substituted by the build system with the actual qualifier. The default for this is the date and time ('YYYYMMDDHHMM'). This can be overridden using a 'forceContextQualifier' property (exactly how you do this depends on which build system you are using).

More details in the help here

Upvotes: 3

Related Questions