[ 
https://issues.apache.org/jira/browse/SLING-11616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693081#comment-17693081
 ] 

Julian Reschke edited comment on SLING-11616 at 2/24/23 8:57 AM:
-----------------------------------------------------------------

bq. this is obivously not a valid file name on windows

Well, the FS supports that (I can roundtrip between Cygwin and WSL just fine). 
It's just that the Windows command shell and Explorer are confused. I believe 
these should be fine.

EDIT:

so it's
{noformat}
java.nio.file.InvalidPathException: Illegal char <:> at index 4: 
/oak:index/lucene/tika/config.xml
        at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
        at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
        at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
        at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
        at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
        at java.nio.file.Paths.get(Paths.java:84)
{noformat}

So it is Java on Windows which is extra-picky, not Windows itself.

So maybe modify the test to leave out ":".


was (Author: reschke):
bq. this is obivously not a valid file name on windows

Well, the FS supports that (I can roundtrip between Cygwin and WSL just fine). 
It's just that the Windows command shell and Explorer are confused. I believe 
these should be fine.

> 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)

Reply via email to