hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giridharan Kesavan <gkesa...@hortonworks.com>
Subject Re: Picking up local common changes in mr
Date Thu, 18 Aug 2011 23:17:16 GMT
>> populated into my local m2 repo but it is not picked up by mvn
>> test-compile -Dresolvers=internal

mvn doenst understand -Dresolvers=internal. (this is an ant/ivy configuration).

by default maven resolves artifacts from the local cache and if not
available then resolves from the mvn repository.

you could try with ant veryclean


On Thu, Aug 18, 2011 at 3:42 PM, Eli Collins <eli@cloudera.com> wrote:
> Thanks Giri.  That doesn't seem to work from me. Eg if I make a change
> to FileUtil in hadoop-common then mvn-install -DskipTests, it gets
> populated into my local m2 repo but it is not picked up by mvn
> test-compile -Dresolvers=internal in hadoop-mapreduce (ie per below I
> can't introduce a new method that's used in a test). Does this work
> for you or am I doing something wrong?
>
> Thanks,
> Eli
>
> hadoop-mapreduce (trunk)$ git diff
> diff --git hadoop-common/src/main/java/org/apache/hadoop/fs/FileUtil.java hadoop
> index 8e7aa30..0471caf 100644
> --- hadoop-common/src/main/java/org/apache/hadoop/fs/FileUtil.java
> +++ hadoop-common/src/main/java/org/apache/hadoop/fs/FileUtil.java
>
> +  public static boolean fullyDelete2(File dir) { }
> +
>
> diff --git hadoop-mapreduce/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apa
> index 454ef2c..d029529 100644
> --- hadoop-mapreduce/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/had
> +++ hadoop-mapreduce/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/had
> @@ -1,3 +1,4 @@
>     } finally {
>       FileUtil.fullyDelete(procfsRootDir);
> +      FileUtil.fullyDelete2(procfsRootDir);
>     }
>   }
>
>
>
>
> On Thu, Aug 18, 2011 at 3:30 PM, Giridharan Kesavan
> <gkesavan@hortonworks.com> wrote:
>> Hello,
>>
>> Its the same -Dresolvers=internal for the ant build system; For the
>> maven/yarn build system as long as you have the latest common jar in
>> the m2 cache its going to resolve common from the maven cache. If not
>> from the apache maven repo. You can force the builds to use the cache
>> by adding -o option. (offline builds)
>>
>> Thanks,
>> Giri
>>
>> On Thu, Aug 18, 2011 at 3:19 PM, Eli Collins <eli@cloudera.com> wrote:
>>> Hey gang,
>>>
>>> What's the new equivalent of resolvers=true in the new MR build? ie
>>> how do you get a  a local common change to get picked up by mr?
>>>
>>> Thanks,
>>> Eli
>>>
>>
>

Mime
View raw message