Maven 1.x Ear Plugin

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.6, 1.6.1
• Fix Version/s: 1.7
• Component/s: None
• Labels:

  None
• Environment:

  Linux

Many of our projects have a seperate maven.repo.local defined, to ease development with multiple branches. Typically an ear sub project will have a property of:

maven.repo.local = ${basedir}/../maven-rep

Sadly, the case sensitive checking of the ear plugin gets rather confused by this issueing a warning for any dependency definition. Version 1.6.1 shows the problem that the located path value contains the .. charcters and so never matches the absolute path for the dependency. ie.:

############################################################################

1. WARNING: possible case-sensitiveness issue within a dependency #
   ############################################################################
2. Looks like a the dependency was either retrieved in the past with the #
3. wrong case or has been specified with the wrong case in your project.xml #
4. file. If that is the case, fix your project.xml or update your local #
5. repository with the properly-cased file and try again. #
6. #
7. Reason for the warning: #
8. the dependency quartz:quartz is located at:
   '/tmp/checkout/project/subproject/../maven-rep/quartz/jars/quartz-1.4.0.jar'
9. but was expected to be located at:
   '/tmp/checkout/project/maven-rep/quartz/jars/quartz-1.4.0.jar'
   ############################################################################

These two paths are the same location!

No other plugins in our projects cause this problem, so either ear has taken upon itself to do this checking, or it handles it differently to others (jar, war).

• Assignee:

  Felipe Leme

  Reporter:

  Kevin Pearcey

• Created:

  22/Dec/04 11:07 AM

  Updated:

  16/Jan/05 8:48 PM

  Resolved:

  16/Jan/05 8:48 PM