aboutsummaryrefslogtreecommitdiff
path: root/project/build.properties
diff options
context:
space:
mode:
authorPrashant Sharma <prashant.s@imaginea.com>2014-10-22 19:44:00 -0700
committerPatrick Wendell <pwendell@gmail.com>2014-10-22 19:44:00 -0700
commitc5882c663e054adcd3ecd9f11e91a1929dbc14a3 (patch)
tree0ab8032b5fc0d94e912b17a42a4cb622c27c1642 /project/build.properties
parent137d94235383cc49ccf8a7bb7f314f578aa1dede (diff)
downloadspark-c5882c663e054adcd3ecd9f11e91a1929dbc14a3.tar.gz
spark-c5882c663e054adcd3ecd9f11e91a1929dbc14a3.tar.bz2
spark-c5882c663e054adcd3ecd9f11e91a1929dbc14a3.zip
[SPARK-3812] [BUILD] Adapt maven build to publish effective pom.
I have tried maven help plugin first but that published all projects in top level pom. So I was left with no choice but to roll my own trivial plugin. This patch basically installs an effective pom after maven install is finished. The problem it fixes is described as follows: If you install using maven ` mvn install -DskipTests -Dhadoop.version=2.2.0 -Phadoop-2.2 ` Then without this patch the published pom(s) will have hadoop version as 1.0.4. This can be a problem at some point. Author: Prashant Sharma <prashant.s@imaginea.com> Closes #2673 from ScrapCodes/build-changes-effective-pom and squashes the following commits: aa7b91d [Prashant Sharma] used an unused dep. 0300dac [Prashant Sharma] improved comment messages.. 28f891e [Prashant Sharma] Added a useless dependency, so that we can shade it. And realized fake shading works for us. 553d96b [Prashant Sharma] Shaded some unused class of an unused dep, to generate effective pom(s)
Diffstat (limited to 'project/build.properties')
0 files changed, 0 insertions, 0 deletions