[
https://issues.apache.org/jira/browse/SLING-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Saar updated SLING-365:
---------------------------------
Attachment: checkin-initial-content.diff
The patch allows two ways for controling the checkin behaviour. The general
behaviour is as follows:
1. A bundle header <Sling-Checkin-Versionables/> (with boolean value) can be
added that can be used to specify if versionable nodes should be checked in. If
set to TRUE all versionable nodes will be checked in.
2. If the bundle header is missing or set to FALSE, the protected property
jcr:isCheckedOut is taken into account. This means if this property is set to
FALSE on a versionable node in the inital content definition, then the node
will be checked in at the end of the import. In case the property is missing or
set to TRUE the node will not get checked in.
Because jcr:isCheckedOut is protected, it will not be set directly on the node,
but after the checkin the resulting node hierarchy will match the definition of
the initial content.
> Checkin versionable nodes in initial content
> --------------------------------------------
>
> Key: SLING-365
> URL: https://issues.apache.org/jira/browse/SLING-365
> Project: Sling
> Issue Type: Improvement
> Components: Resource
> Reporter: Alexander Saar
> Attachments: checkin-initial-content.diff
>
>
> As discussed in [1] a bundle developer should be able to decide wether a
> versionable node in his initial content should be checked in after the
> content is imported or not.
> [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg03804.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
