Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-dev@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAJs-t7OC3D-_g_PpW9emWXMZaLqEGgD0zRZ=B73bJxcdOw9+CQ@mail.gmail.com>
References: 
 <CAPn_vTtWtqSdhiu1X_x6kGPuxuQdJKTqjaBUzCtJcYbO8Y0W6Q@mail.gmail.com>
 <CANJr2=FZTULcXAzu7M4VU+e6YY6FJkFHH2-EJJ75c6JFtYDowQ@mail.gmail.com>
 <CA+z3+9EfLoHi=-ASQGd4RiR84AadvvPdxCeF+U75DdSmWMmxPQ@mail.gmail.com>
 <CAJs-t7OC3D-_g_PpW9emWXMZaLqEGgD0zRZ=B73bJxcdOw9+CQ@mail.gmail.com>
From: Matt Foley <mfoley@hortonworks.com>
Date: Fri, 19 Aug 2011 09:41:08 -0700
Message-ID: 
 <CA+z3+9F7TC9-m1RnH4R_tA2k_vjtnpPX6RtuSTQ9cV_3J3bYBw@mail.gmail.com>
Subject: Re: Picking up local common changes in mr
To: mapreduce-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0016367657cd3f139d04aade67fd

--0016367657cd3f139d04aade67fd
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the nice clear statement, Alejandro.
--Matt

On Thu, Aug 18, 2011 at 4:40 PM, Alejandro Abdelnur <tucu@cloudera.com>wrote:

> This is handled by maven reactor.
>
> When your run Maven in a multimodule project (like we have), all modules
> that are part of the build (from the dir where you are) down are used for
> the build/test/packaging, all modules that are not part of the build are
> picked up from .m2/repo.
>
> For example
>
> "cd trunk/hadoop-mapreduce;mvn compile" uses hadoop-common & hadoop-hdfs
> from m2/repo
>
> "cd trunk;mvn compile" uses hadoop-common, hadoop-hdfs, hadoop-mapreduce
> from the build.
>
> HTH
>
> Thxs.
>
> Alejandro
>
>
> On Thu, Aug 18, 2011 at 4:35 PM, Matt Foley <mfoley@hortonworks.com>
> wrote:
>
> > 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 :-)
> >
> > --Matt
> >
> > 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
> > > >
> > >
> >
>

--0016367657cd3f139d04aade67fd--