hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Foley <mfo...@hortonworks.com>
Subject Re: Picking up local common changes in mr
Date Thu, 18 Aug 2011 23:35:13 GMT
Since we put all the effort into "un-splitting" the components, shouldn't we
have a switch
that causes, eg, the MAPREDUCE build to pick up artifacts from COMMON and
HDFS builds
in specified sibling directories, without using m2 as an intermediary?

Of course it should respect dependencies (via maven) so that if HDFS source
has been modified,
the HDFS artifacts will also be rebuilt before MAPREDUCE uses them :-)


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
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message