The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 8 Dec 2004 6:19 AM
Body:
Ludovic,
That message is caused by a change on the maven-ear-plugin (MPEAR-9).
Looks like the fix for that issue breaks some cases where the MAVEN_HOME is set
with different cases - please take a look on the comments on the MPEAR-9 and
give us your feedback.
Thanks (and sorry for the problem),
-- Felipe
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1526?page=comments#action_27615
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1526
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1526
Summary: Regression: build fails because of case problem in dependency
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1-beta-1
Versions:
1.0.2
Assignee:
Reporter: Ludovic Claude
Created: Wed, 8 Dec 2004 6:02 AM
Updated: Wed, 8 Dec 2004 6:19 AM
Environment: Windows XP
Description:
I have updated from maven 1.0.1 to maven 1.0.2, and now my build fails with the
following error message:
Case-sensitive issue: The dependency commons-httpclient:commons-httpclient has
a case problem. The dependency was eithe
r retrieved in the past with the wrong case or has been specified with the
wrong case in your project.xml file. Fix you
r project.xml or update your local repository with the properly-cased file and
try again.
I checked again and again, and in my project.xml commons-httpclient is spelled
in lowercase, and in the maven repository it is also lowercase. Please update
the error message and provide more information about the origin of this error,
and don't fail on this issue but only provide a warning.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
