The following comment has been added to this issue:
Author: Felipe Leme
Created: Thu, 9 Dec 2004 7:37 AM
Body:
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
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPEAR-9?page=comments#action_27710
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPEAR-9
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPEAR-9
Summary: Dependency case mismatch causes missing dependency without error
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-ear-plugin
Fix Fors:
1.6.1
Versions:
1.2
Assignee:
Reporter: Sean Timm
Created: Mon, 10 Nov 2003 7:30 PM
Updated: Thu, 9 Dec 2004 7:37 AM
Environment: Windows (or any other operating system setup to allow
case-insensitive retrieval of dependencies from the repository)
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.
---------------------------------------------------------------------
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]
