[jira] Closed: (MPEAR-35) case-sensitive dependency check can't handle relative repo paths

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Felipe Leme
       Date: Sun, 16 Jan 2005 8:48 PM

I'm removing the dependency checking, as it is causing too much hassle.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPEAR-35

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPEAR-35
    Summary: case-sensitive dependency check can't handle relative repo paths
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-ear-plugin
   Fix Fors:
             1.7
   Versions:
             1.6
             1.6.1

   Assignee: Felipe Leme
   Reporter: Kevin Pearcey

    Created: Wed, 22 Dec 2004 11:07 AM
    Updated: Sun, 16 Jan 2005 8:48 PM
Environment: Linux

Description:
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.:

############################################################################
#      WARNING: possible case-sensitiveness issue within a dependency      #
############################################################################
# Looks like a the dependency was either retrieved in the past with the    #
# wrong case or has been specified with the wrong case in your project.xml #
# file. If that is the case, fix your project.xml or update your local     #
# repository with the properly-cased file and try again.                   #
#                                                                          #
# Reason for the warning:                                                  #
# the dependency quartz:quartz is located at:
'/tmp/checkout/project/subproject/../maven-rep/quartz/jars/quartz-1.4.0.jar'
# 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).


---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org