Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 439109

Summary: Revert the systematic version bump on Export-Package
Product: [Modeling] Sirius Reporter: Pierre-Charles David <pierre-charles.david>
Component: CoreAssignee: Project inbox <sirius.core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: maxime.porhel
Version: 1.0.0Keywords: triaged
Target Milestone: 1.0.1   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 440884    

Description Pierre-Charles David CLA 2014-07-08 04:32:16 EDT 
Right after the 1.0.0 release, we created a v1.0.x maintenance branch, and the first commit on that branch (a3b8683cf236e95748e25c94be673c88768d7a96) was to bump the version number globally to 1.0.1. The bumpd was performed globally, on all feature and bundles versions, and an all exported packages versions. I'm not clear yet on what is the correct thing to do from an OSGi point of view, but such a global change is too broad.
Comment 1 Pierre-Charles David CLA 2014-07-08 04:37:45 EDT 
Proposal: only bump to 1.0.1 the version of exported packages where there is at least one change since 1.0.0, and the plug-ins/bundles which contain at least one such package, and the features which include at least one such plug-in.

This minimizes the changes but keeps the expectation that a bundle's (resp. feature's) version is the max all its exported packages (resp. bundles) versions.
Comment 2 Pierre-Charles David CLA 2014-08-05 09:12:34 EDT 
After discussion with people more knowledgeable than me on OSGi technicalities, it seems that while not ideal the global bump to 1.0.1 can not cause actual issues in practice. We'll try to use a more precise approach for the next major version, but for the 1.0.x maintenance stream we'll keep the simple global bump as it is.