You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bigtop.apache.org by Jay Vyas <ja...@gmail.com> on 2014/02/21 23:14:59 UTC
Where does source actually come from ?
Hi bigtop !
I noticed that there are 2 locations of bigtop dependencies:
1) The pom.xml file
2) The explicit links in "bigtop.mk"
So in the end, what is bigtop pulling the actual jar file used in the
distirbution from?
I ask this because, looking at hue, it was interesting: It is in not in the
maven pom.xml , and references the cloudera/archives github repository for
the source in the mk file.
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Where does source actually come from ?
Posted by Jay Vyas <ja...@gmail.com>.
thanks sean. but im wondering , then, why there is a maven definition of
the sources (in pom.xml) as well as bigtop.mk.
Who is really doing the download and where?
Thanks !
On Fri, Feb 21, 2014 at 5:23 PM, Sean Mackrory <ma...@gmail.com> wrote:
> bigtop.mk links to the source distribution, and when you build packages
> those sources are downloaded, built, and the JARs that get built are
> included in the packages that then get hosted. Since Bigtop does not, as a
> rule, patch upstream projects, these JARs are identical (in theory,
> anyway), to the JARs another project might get if it were to download the
> JARs for that component using Maven.
>
>
> On Fri, Feb 21, 2014 at 2:14 PM, Jay Vyas <ja...@gmail.com> wrote:
>
>> Hi bigtop !
>>
>> I noticed that there are 2 locations of bigtop dependencies:
>>
>> 1) The pom.xml file
>>
>> 2) The explicit links in "bigtop.mk"
>>
>> So in the end, what is bigtop pulling the actual jar file used in the
>> distirbution from?
>>
>> I ask this because, looking at hue, it was interesting: It is in not in
>> the maven pom.xml , and references the cloudera/archives github repository
>> for the source in the mk file.
>>
>> --
>> Jay Vyas
>> http://jayunit100.blogspot.com
>>
>
>
--
Jay Vyas
http://jayunit100.blogspot.com
Re: Where does source actually come from ?
Posted by Sean Mackrory <ma...@gmail.com>.
bigtop.mk links to the source distribution, and when you build packages
those sources are downloaded, built, and the JARs that get built are
included in the packages that then get hosted. Since Bigtop does not, as a
rule, patch upstream projects, these JARs are identical (in theory,
anyway), to the JARs another project might get if it were to download the
JARs for that component using Maven.
On Fri, Feb 21, 2014 at 2:14 PM, Jay Vyas <ja...@gmail.com> wrote:
> Hi bigtop !
>
> I noticed that there are 2 locations of bigtop dependencies:
>
> 1) The pom.xml file
>
> 2) The explicit links in "bigtop.mk"
>
> So in the end, what is bigtop pulling the actual jar file used in the
> distirbution from?
>
> I ask this because, looking at hue, it was interesting: It is in not in
> the maven pom.xml , and references the cloudera/archives github repository
> for the source in the mk file.
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com
>