nodejs based sling packager

[Ruben Reusser]

Dear Sling Developers,

in an effort to help 'front end developers' embrace Apache Sling and in 
order to make simple front-end Sling projects maven independent we 
created a node only slingpackager [1] and a sample VueJs based Slnig 
Content Browser [2] as a showcase project.


We'd like to see the slingpackager (and potentially the showcase 
example) be part of Apache Sling and maybe live on npmjs in an Apache 
Sling organization (@apachesling for example).


We'd love to hear what you think about this!

Ruben Reusser

[1] https://github.com/peregrine-cms/slingpackager
[2] https://github.com/peregrine-cms/simple-sling-vue-example

[jira] [Resolved] (SLING-8578) Nodes which contain : are not correctly processed

[Simone Tripodi (JIRA)]

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

Simone Tripodi resolved SLING-8578.
---
Resolution: Fixed
  Assignee: Simone Tripodi

PR merged on master

> Nodes which contain : are not correctly processed
> -
>
> Key: SLING-8578
> URL: https://issues.apache.org/jira/browse/SLING-8578
> Project: Sling
>  Issue Type: Bug
>  Components: Content-Package to Feature Model Converter
>Reporter: Andrei Tuicu
>Assignee: Simone Tripodi
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> h3. Problem
> Nodes that contain : character are put in content packages with the help of _ 
> , for example the following path /content/cq:tags/somenode in AEM would look 
> in the content package like:
> /jcr_root/_cq_tags/somenode .  This is done because Windows does not accept : 
> in the name of it's files/folders.
> If the content package converter would process this path it would generate a 
> the following repo:init lines
> {code}
> "create path (sling:Folder) /content/_cq_tags",
> "create path (cq:Tag) /content/_cq_tags/somenode",
> {code}
> Similar, if there are rep policies under that path, the output would look as 
> following:
> {code}
> "set ACL for my-system-user",
> "allow 
> jcr:versionManagement,jcr:read,rep:write,crx:replicate,jcr:lockManagement on 
> /content/_cq_tags/somenode",
> {code}
> This results in the wrong node structure in the AEM instance, as follows:
> {code}
> /content
>/cq:tags### <- original AEM folder
>/_cq_tags   ###<- folder created by the repoinit statements
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)