aboutsummaryrefslogtreecommitdiff
path: root/bigtop-packages
diff options
context:
space:
mode:
authorRob Leidle <leidle@amazon.com>2015-04-21 09:47:57 -0700
committerKonstantin Boudnik <cos@wandisco.com>2015-04-21 14:06:52 -0700
commit56e49d5fa38e4fc566d7cb8ca9dda31a8ae6f4fd (patch)
tree9f6511228e330288a94bf94a2488b721300133ff /bigtop-packages
parentf0be77f43e51dbe271b5ee080364ec5ffd66fa0c (diff)
BIGTOP-1838: Publish results of pig build to local ivy/maven repositories
The pig build does not execute the published target. This means that other pieces of the bigtop ecosystem do not pick up the correct pig dependencies from the bigtop build. Instead, they pick them up from the central maven repository (or they fail to find them if a bigtop has pig version that is not publicly released). This is a problem because builds like datafu pick up their pig dependency via ivy and they are not able to do so. Signed-off-by: Konstantin Boudnik <cos@wandisco.com>
Diffstat (limited to 'bigtop-packages')
-rw-r--r--bigtop-packages/src/common/pig/do-component-build2
1 files changed, 1 insertions, 1 deletions
diff --git a/bigtop-packages/src/common/pig/do-component-build b/bigtop-packages/src/common/pig/do-component-build
index 350a0fa9..5c210a38 100644
--- a/bigtop-packages/src/common/pig/do-component-build
+++ b/bigtop-packages/src/common/pig/do-component-build
@@ -59,7 +59,7 @@ done
echo "forrest.maxmemory=256m" >> src/docs/forrest.properties
export ANT_OPTS="-Xmx4096m"
-ant $BUILD_OPTS clean jar pigunit-jar smoketests-jar javadoc "$@"
+ant $BUILD_OPTS clean published pigunit-jar smoketests-jar javadoc "$@"
for build_file in contrib/piggybank/java/build.xml ; do
ant $BUILD_OPTS -buildfile $build_file clean jar "$@"
done