I'm hosting an in-house remote repository via Apache 2 on a Windows server. I recently ran into an issue where a few projects specified the name of a dependency with the wrong case (all lowercase instead of mixed-case). The remote repository still treats it as a valid filename and returns the dependency, but it is now in the local repository with the wrong case, and this caused a bit of a problem.
At this point, I did an ear:ear, and the creation of the EAR was successful, but one of the dependencies was missing. It turns out it was due to another component having originally specified it with the wrong case, and it just maintained the wrong case from then on out. I'm trying to figure out the best way to handle this. Does anyone know if it's possible to force Apache for Windows to be case-sensitive for a specific file request? Irregardless, the EAR plugin should have failed when it didn't successfully add the artifact, so it looks like there's a problem there, too, so I'll take a look at it... -- Sean T.
