[ 
https://issues.apache.org/jira/browse/GIRAPH-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237616#comment-13237616
 ] 

Brian Femiano commented on GIRAPH-159:
--------------------------------------

giraph-0.2-SNAPSHOT-jar-with-dependencies.jar goes from being ~5MB in size to 
~34MB once all the
hbase dependencies are unpacked.  

mvn verify takes about 1.5 hours to run with the pseudo-distributed unit tests. 

                
> Case insensitive file/directory name matching will produce errors on M/R jar 
> unpack. 
> -------------------------------------------------------------------------------------
>
>                 Key: GIRAPH-159
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-159
>             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: 
> https://issues.apache.org/jira/browse/MAHOUT-780
> I've been able to reproduce this on my local OSX install with the following 
> error:
> https://groups.google.com/a/cloudera.org/group/cdh-user/browse_thread/thread/a201218000e956d3/cc6eca3ef9f80ff8
> 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to