Thanks Florian... Do you mean to say that the properties on the repository defines the major and minor versioning of files? If so, how can we adjust that.
Similarly using CMIS we can set either minor or major versions or can we change the minor/major versioning on the fly during checkin. Regards, Ram Mahesh Kumar K -----Original Message----- From: Florian Müller [mailto:f...@apache.org] Sent: 14 June 2018 02:19 To: dev@chemistry.apache.org; K, Rammaheshkumar Subject: Re: Reg: Major/Minor Version - CMIS Hi, the definition of major and minor versions depends on the repository. For CMIS major and minor versions are only abstract concepts. Many repositories use 1.0, 2.0, 3.0, ... as major versions and 1.1, 1.2, 1.3, ... as minor versions. But this is not a strict rule. Please consult the documentation of your repository. - Florian > Hi, > > Can you please help me in understanding if we can create minor versions > during checkin using CMIS. > > If file does not exist, > > document = subFolder.createDocument(props, contentStream, > VersioningState.MAJOR); - Will there be any impact changing this versioning > state to MINOR? > > If file exists, > > contentStream = > session1.getObjectFactory().createContentStream(fileName, > inFile.length(), fileType, new FileInputStream(inFile)); ObjectId > objectId = pwc.checkIn(false, null, contentStream, "Testing of > versioning."); > > The above are the set of codes that I found in Apache Chemistry website and > using the same I able to create versions of a file. Example, the versions > created now are like 1.0, 1.1, 1.2 etc., I would like to know if it is > possible to create minor versions like 1.1.1,1.1.2 etc. Or at least create > major versions like 1.0, 2.0 etc. and 1.0, 1.1 as minor versions. > > Regards, > > Ram Mahesh Kumar K > >
