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 <[email protected]> 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 >
