Some static analysis tools that run on Windows report warnings with a path that might use the wrong capitalization. This has no effect on Windows but will influence several aspects of the warnings plugin: absolute path resolving, fingerprinting, copying of source files to Jenkins agent. If the path uses the wrong capitalization, then the file is not valid for the warnings plugin even though it might be in the sense of the Windows file system.

Therefore it would make sense to change all those functionalities so that they use case-insensitive matching.