Versioning - support to change major version number

[sipos-roland-13b18346]

When I check in a new version of a node, Modeshape assigns a version number to it automatically, with format majorNumber.minorNumber.
My problem is, with each new version, Modeshape increases the minor version number, and leaves the major version unchanged, which always stays at 1.

I would like to be able to change the major version number, but I can't find a way to do this.
More specifically, I would like to tell Modeshape whether the major number, or the minor number should be inremented with each new version.

Is there a way to do that? Am I missing something?
If not, are there any plans to add support for low level version number handling in the future?

I'm pretty sure i'm missing something here, it's hard to imagine that Modeshape supports versioning, but doesn't let me create meaningful version numbers, which would include the ability to change major version as well.    

[hchiorean]

The name of the version nodes is an internal implementation detail, not something which is meant to be exposed and used by clients directly (actually the entire structure of nodes created under a version history should be consider internal, with the exception of the parts which JCR #3.13 exposes explicitly). The public versioning API includes classes like javax.jcr.version.VersionManager, javax.jcr.version.VersionHistory etc

If you want some sort of semantical meaning for the different versions you can use version labels (see JCR 2.1 #3.13.5.5) or create some other custom logic specific to your application.

[sipos-roland-13b18346]

Thanks for the advice.