Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.2
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Windows (or any other operating system setup to allow case-insensitive retrieval of dependencies from the repository)
-
Number of attachments :
Description
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've modified the EAR plugin to check for this inconsistency and error out if it's detected, and I'll attach a patch shortly. Note that the WAR plugin may have this issue, too, but I haven't taken a look it it, yet.
Attachments
Issue Links
| This issue is superceded by: | ||||
| MPEAR-37 | Remove dependency warning |
|
|
|
| This issue is depended upon by: | ||||
| MAVEN-1526 | Regression: build fails because of case problem in dependency |
|
|
|
Activity
It seems to partially work. I have the following in by build.properties:
maven.home.local=${maven.home}
maven.repo.local=${maven.home}/repository
MAVEN_HOME=c:\maven-1.0.1
The check is too powerful in this case. It compares the absolute path:
c:\maven-1.0.1\repository\mycompany\jars\myjar.jar
with the canonical:
C:\maven-1.0.1\repository\mycompany\jars\myjar.jar
Driver letter case changes between both. The workaround is to modify the MAVEN_HOME to have a capital C.
If I understood the fix correctly, I think the goal is to check only the jar name or maybe the jar and the group, not the complete path. That would solve the issue.
And I think you will hate working on the issue if you use Linux 
I'm marking as fixed, but will cut the release only this Saturday - so users will have more time testing it
I will be releasing maven-ear-plugin 1.6.1 over the weekend. Meanwhile, I provided a 'pre-release' to be tested by those having these issues.
You can install it using the following command:
maven plugin:download -Dmaven.repo.remote=http://apache.org/~felipeal/maven_repo -DgroupId=maven -DartifactId=maven-ear-plugin -Dversion=1.6.1-SNAPSHOT
So, for those having issues with the ear plugin bundled with Maven 1.0.2, please try this new version and let us know the result.
Thanks (and sorry for the hassle
– Felipe
– Felipe
Here's the patch to fix it...