Eclipse Platform: Strict Plugin Versioning to be enforced in E3.2
It would appear that the Eclipse Platform, or actually the new-ish Equinox (OSGI runtime) project have finally decided to eat their own dog food and address “the poor practice of not versioning Eclipse“) for their 3.2 release.
If you are skimming, comment #50 is the most important response I think – also #25, #27, #30, #32, #40 are good contributions.
They have published a versioning best practices document that is incredibly complicated but (given the length of the bugzilla thread) it would seem a lot of thought has gone into finding a system that works for both maintenance and forward dev branches.
About time if you ask me, the lack of strict version specification in the Eclipse platform has lead everyone downstream to believe it was ok to do the same, leading to an almighty mess and in most cases making it impossible to use the update manager to reliably install multiple unrelated features into the same Eclipse installation.
Now they’ll just have to get all those other projects to follow their lead…
Recent Comments