Affects Version/s: None
Fix Version/s: None
The JCR API bundle/library exports the JCR API at version 2.0 – specifically the API is exported with the same version as the bundle version.
Compared to JCR 1.0 (JSR-170) this signifies a major version change. According to the OSGi Semantic Versioning recommendation  a major version change on an exported package indicates backwards incompatible changes.
It is my understanding, though, that JCR 2.0 is fully backwards compatible with JCR 1.0 hence the API exports should not indicate backwards incompatiblity.
As a fix I propose to export the API with two versions:
1.1 to support OSGi bundles written against the JCR 1.0 API and
importing with recommended version range [1.0,2)
2.0 to not break bundles written against the JCR 2.0 API bundle