incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (Commented) (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-159) Case insensitive file/directory name matching will produce errors on M/R jar unpack.
Date Sat, 24 Mar 2012 06:29:22 GMT


Avery Ching commented on GIRAPH-159:

Brian, I am able to run the distributed unittests just fine on my single node hadoop install.

jar tvf giraph-0.2-SNAPSHOT-jar-with-dependencies.jar  | grep -i license
 11358 Mon Mar 16 00:31:16 PDT 2009 META-INF/LICENSE.txt
   580 Mon Jun 07 20:50:48 PDT 2010 META-INF/LICENSE
 11358 Fri Jan 21 17:06:30 PST 2011 LICENSE.txt

I don't have a license directory.  What does your jar say?
> Case insensitive file/directory name matching will produce errors on M/R jar unpack.

> -------------------------------------------------------------------------------------
>                 Key: GIRAPH-159
>                 URL:
>             Project: Giraph
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.2.0
>         Environment: OSX 10.6.8
>            Reporter: Brian Femiano
>         Attachments: GIRAPH-159.patch, compile.xml
> This only seems to affect platforms where there can be a file/directory naming conflicts
> from case insensitive matches. 
> I was able to reproduce running the pseudo-distributed unit tests within OSX.
> This has affected other projects: 
> I've been able to reproduce this on my local OSX install with the following error:
> Since LICENSE.txt contains the same content as the file LICENSE, I propose we exclude
any LICENSE matches found in the unpacked dependency jars
> when the maven assembly phase hits 'jar-with-dependencies'. 
> I have a patch which moves the 'jar-with-dependencies' descriptor to an external compile.xml
file which has the proper excludes. This might also
> come in handy down the road should any additional tweaks be needed to the compile phase.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message