[NXP-19827] Fix versioning option when no version is needed - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 7.10
Fix Version/s: 7.10-HF12, 8.3
Component/s: Nuxeo Drive

Tags:
- SupCom
Impact type:

Data Persistence Change
Upgrade notes:

Hide

Now Drive always send a versioning option, which is useful when an automatic versioning is configured: when a change is recently done, the document is not checked in, but just save as a draft.

To retrieve the previous behavior
<extension target="org.nuxeo.runtime.ConfigurationService"
point="configuration">
<documentation>
Force Drive not to send its versioning option even if no minor/major increase
is needed.
</documentation>
<property name="nuxeo.drive.force.versioning">false</property>
</extension>

Show
Now Drive always send a versioning option, which is useful when an automatic versioning is configured: when a change is recently done, the document is not checked in, but just save as a draft. To retrieve the previous behavior <extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <documentation> Force Drive not to send its versioning option even if no minor/major increase is needed. </documentation> <property name="nuxeo.drive.force.versioning">false</property> </extension>

Description

When no version increment is needed, that means the rules to increase the version are not satisfied, Drive does not explicitly set the versionning option to follow.
Therefore the versioning option will be decided by the backend whereas it should follow Drive directive.

In all cases, Drive should set the versioning option.

Attachments

Activity

People

Assignee:

Thierry Martins

Reporter:

Thierry Martins

Participants:

Jenkins, Thierry Martins

Votes:

0 Vote for this issue

Watchers:

2 Start watching this issue

Dates

Created:

2016-06-14 08:33

Updated:

2016-12-02 14:44

Resolved:

2016-06-30 13:18

Time Tracking

Estimated:

Not Specified

Remaining:

Logged: