[SLING-10821] Support resource types with characters invalid in zip entry names

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Scripting Bundle Maven Plugin 0.4.0
• Fix Version/s: Scripting Bundle Maven Plugin 0.5.4
• Component/s: Maven Plugins and Archetypes
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 17/Sep/21 09:05
• Updated: 16/Dec/21 13:40

Description

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.