Hello,
Just to give a brief introduction, we are working on a solution which we are developing on top of Adobe Experience Manager (which is built upon Jackrabbit Oak). We have a requirement from one of our customer , where they want to keep versionable data in JCR repository. They need advanced version management capabilities where user can create minor and major versions of a node. I went through “Versioning Model” section of JCR 2.0 Specification (JSR 283). My understanding of that section is that JCR specification does not enforce whether the implementation can do only minor or major versioning. *“Each version has a name unique within its version history that is assigned automatically on creation of the version. The format of the name is implementation-dependant.”* And hence correspondingly in javax.jcr.version.VersionManager.checkin(java.lang.String absPath) API, the version name is auto-generated by system. Now for oak 2.0, I see this version name is always generated by doing a minor increment for e.g. from 1.1 -> 1.2 -> 1.3. So apparently it seems oak 2.0 is creating “Version Name” by doing minor version number increment. I just wanted to know if there are any plans to support a major version increment in future? Or even in current implementation, is there a scenario under which a new Version object is created with a name which is generated by incrementing the first number in version name for e.g. 1.0 -> 2.0 -> 3.0 ? Also, I was browsing through the code and I could not locate the file which contains this logic for determining the version name for new Version object. Any help on that source file path will be appreciated. Thanks, Tulika
