Franca Eclipse feature version 0.9.0 violating semantic versioning rule

[GoogleCodeExporter]

Franca 0.9.0 Eclipse plugin is incompatible to Franca 0.8.x according to Franca 
release notes.
When creating a new Eclipse target platform to build CommonApi tools, the 
Eclipse dependency check automatically selects version 0.9.0 instead of 0.8.x 
versions as it considers 0.9.0 as compatible upgrade (same major version).

Eclipse decided to use interface versions according to 
http://eclipsesource.com/blogs/2013/06/28/semantic-versioning-for-eclipse-develo
pers/, which is matching well to http://semver.org/ specification used by 
GENIVI.

An incompatible Eclipse feature should have an increased major version.

Original issue reported on code.google.com by manfred....@bmw.de on 19 May 2014 at 1:36

[GoogleCodeExporter]

This cannot be resolved easily. We are aware of the semantic versioning scheme. 
However, until the project has become an Eclipse project and passed its 
incubation phase, we cannot increase the major number from 0.x to 1.0. For 
Eclipse projects, this step can only be done after passing the incubation 
phase. And as we are planning to contribute Franca to Eclipse and want to 
ensure version continuity across the transition from now (google.code hosted) 
to Eclipse, we have to stay in the version range 0.x.

However, we are aiming to adhere to the following scheme until we can use the 
major part:
- major part sticks to 0
- increase in minor part: if there are changes which could break backward 
compatibility
- increase in patch part: if there were no changes breaking backward 
compatibility

Pls comment on this or provide a better solution.

Original comment by klaus.birken@gmail.com on 10 Nov 2014 at 12:13

• Changed state: Accepted

[GoogleCodeExporter]

Sorry, this cannot be handled 100% correct until transition to Eclipse 
Foundation is accomplished. See previous comment for a detailed explanation.

Original comment by klaus.birken@gmail.com on 8 May 2015 at 8:12

• Changed state: WontFix