[jira] [Updated] (SLING-10821) Support resource types with characters invalid in zip entry names

["Karl Pauls (Jira)" <ji...@apache.org>]

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

Karl Pauls updated SLING-10821:
-------------------------------
    Fix Version/s: Scripting Bundle Maven Plugin 0.5.4
                       (was: Scripting Bundle Maven Plugin 0.5.2)

> Support resource types with characters invalid in zip entry names
> -----------------------------------------------------------------
>
>                 Key: SLING-10821
>                 URL: https://issues.apache.org/jira/browse/SLING-10821
>             Project: Sling
>          Issue Type: Bug
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Scripting Bundle Maven Plugin 0.4.0
>            Reporter: Konrad Windszus
>            Priority: Major
>             Fix For: Scripting Bundle Maven Plugin 0.5.4
>
>
> Sling does not limit the character set to use for a resource type. For example a colon is perfectly valid (also in JCR names). As the resource type is directly determined from the zip entry name but the filesystem imposes several limitations (https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations) some kind of escaping need to be supported to allow giving arbitrary resource types just via path name. Filevault Content Packages for example leverage these escaping rules: http://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)