|
||||||||
|
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.
Some comments about case sensitivity behavior: this feature is based entirely on the behavior of case (in)sensitivity of the org.apache.ant:ant:1.8.3 dependency. In particular AbstractFileSet.setCaseSensitive() and DirectoryScanner.setCaseSensitive() (I was able to find online only the 1.6.1 javadoc but I didn't see any difference with the javadoc of the actual 1.8.3 code). There's not much in the javadoc regarding this flag besides a comment in DirectoryScanner : "Case sensitivity may be turned off if necessary. By default, it is turned on. ".
Looking at the code it seems that the library ignore the case-sensitivity of the underlying OS. It does its own processing and does not delegate the matching to the OS. The only thing that comes from the OS are the filenames, the comparisons are made in Java using String.equals() (see for instance DirectoryScanner.isIncluded()).