[
https://issues.apache.org/jira/browse/SLING-11616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693074#comment-17693074
]
Stefan Seifert commented on SLING-11616:
----------------------------------------
[~kwin] the test {{testSlingInitialContentWithSpecialCharacters}} and the used
{{mysite.core-1.0.0-SNAPSHOT-specialchars-json-inputstream.jar}} contains a
JSON file with name:
{noformat}
<"&>.json
{noformat}
this is obivously not a valid file name on windows - and i'm wondering if it's
worth to implement a special handling for such an exotic filename - very
unlikely anyone is using a file name like this. we could add a validation to
fail early with an exception (on both linux and windows) if i filename with
certain not allowed characters is used.
i think this is the only remaining issue.
> Build and test with Windows
> ---------------------------
>
> Key: SLING-11616
> URL: https://issues.apache.org/jira/browse/SLING-11616
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.3.0
> Reporter: Konrad Windszus
> Assignee: Stefan Seifert
> Priority: Major
>
> The ASF Jenkins should build and test on Windows as well to prevent issues
> like SLING-11615.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
