Hi Florian, But at creation or checkin CMIS does provide this option. Shouldn't it be logical to provide the option here as well?
Met vriendelijke groeten, Kind regards, Bien à vous, Mano Swerts Solution Engineer _______________________________________________________ ACA IT-Solutions Ilgatlaan 5C Clovislaan 82 B-3500 Hasselt B-1000 Brussel Belgium Belgium T: +32 (0)11 26 50 10 E: [email protected] F: +32 (0)11 26 50 11 U: www.aca-it.be M: +32 (0)484 80 81 45 ______________________________________________________ On Mon, Jun 18, 2012 at 4:09 PM, Florian Müller <[email protected]> wrote: > Hi Mano, > > This behavior is repository specific. The CMIS interface does not provide > any option to control this. > > > Cheers, > > Florian > > > > Hi all, >> >> We have a batch job that inserts or updates batch content in our >> repository >> using CMIS. It seems to us that updating content would probably be faster >> when done directly instead of using the checkout-checkin method. >> The only problem with this method is that it results in a minor version >> increase instead of a major version. I do not see any option for >> instructing the repository to create a major version on content update >> when >> not using checkout-checkin. >> >> Is there any other way to enforce the major version bump? >> >> Thanks in advance. >> >> Mano Swerts >> > >
