[ https://issues.apache.org/jira/browse/HDFS-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071988#comment-13071988 ]
Joep Rottinghuis commented on HDFS-1935: ---------------------------------------- I solved this in a different way. Do a one-time build to prime the ~/.ivy2 directory and/or copy this from a machine with Internet access. I set the mvn.repo property in ~/build.properties (or pass it in as a -D option). Note that in common this property is called mvnrepo (no dot). mvn.repo=file:/home/jrottinghuis/buildrepo. Then I have two file: /home/jrottinghuis/buildrepo/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar /home/jrottinghuis/buildrepo/org/apache/maven/maven-ant-tasks/2.0.10/maven-ant-tasks-2.0.10.jar The former is needed for all targets, the latter only if you want to use the mvn-install or mvn-publish targets. One other bootstrap problem with this is that the ivy and tasks cannot be found. I therefore manually copy both jars into hadoop-common/hdfs/ivy (also hadoop-common/common/ivy and hadoop-common/mapreduce). In Jenkins I have a simple build step for this. There is still a problem though, and that is that in the compile-contrib target a subant call is made. That does not pass along properties. That is problematic even when one sets other properties (for example hadoop-common.version. I'll file a separate bug for this. > Build should not redownload ivy on every invocation > --------------------------------------------------- > > Key: HDFS-1935 > URL: https://issues.apache.org/jira/browse/HDFS-1935 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 0.22.0 > Reporter: Todd Lipcon > Priority: Trivial > Labels: newbie > Fix For: 0.22.0 > > Attachments: diff, hdfs-1935.patch, hdfs-1935.txt > > > Currently we re-download ivy every time we build. If the jar already exists, > we should skip this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira