|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Maybe. Or it may just be an indication that we need a workaround because otherwise the problem won't go away, possibly never because the JLS guys may decide it to be a feature![]()
I propose to use some platform-specific means for removing such badly encoded files, ie. run "rm -f $strange-filename" on Linux, and the equivalent on Windows. I guess that there are probably already libraries around doing exactly that, though I'm not aware of any.
Another solution would be to let Jenkins always run with a full 8-bit charset as the default charset, ie. one that has no invalid characters/holes in the binary representation per se, though I'm not sure what undesirable side-effects that would bring about.