[jira] Closed: (SLING-365) Checkin versionable nodes in initial content

["Alexander Saar (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Saar closed SLING-365.
--------------------------------


Work for me. But usage is like:

<Sling-Install-Content>
  SLING-INF/content;checkin:=false,
  SLING-INF/checkedin;checkin:=true
</Sling-Install-Content> 

and not 

<Sling-Install-Content>
  SLING-INF/content;checkin=false,
  SLING-INF/checkedin;checkin=true
</Sling-Install-Content> 

After looking into sources I saw it was implemented as a directive and not as attribute, but I guess this is the correct way to do it. 

Thanks a lot.


> Checkin versionable nodes in initial content
> --------------------------------------------
>
>                 Key: SLING-365
>                 URL: https://issues.apache.org/jira/browse/SLING-365
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Resource
>            Reporter: Alexander Saar
>            Assignee: Felix Meschberger
>             Fix For: 2.0.0
>
>         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.