aboutsummaryrefslogtreecommitdiff
path: root/pom.xml
diff options
context:
space:
mode:
authorPatrick Wendell <patrick@databricks.com>2015-07-06 22:14:24 -0700
committerPatrick Wendell <patrick@databricks.com>2015-07-06 22:17:30 -0700
commit1cb2629f1aa466f92246828c562ea6f35c89ab87 (patch)
tree5e55fa2704867205d08cc2ce039a65b62b231511 /pom.xml
parentc46aaf47f38163e9c7be671d7b8398512df34e62 (diff)
downloadspark-1cb2629f1aa466f92246828c562ea6f35c89ab87.tar.gz
spark-1cb2629f1aa466f92246828c562ea6f35c89ab87.tar.bz2
spark-1cb2629f1aa466f92246828c562ea6f35c89ab87.zip
[HOTFIX] Rename release-profile to release
when publishing releases. We named it as 'release-profile' because that is the Maven convention. However, it turns out this special name causes several other things to kick-in when we are creating releases that are not desirable. For instance, it triggers the javadoc plugin to run, which actually fails in our current build set-up. The fix is just to rename this to a different profile to have no collateral damage associated with its use.
Diffstat (limited to 'pom.xml')
-rw-r--r--pom.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/pom.xml b/pom.xml
index fbcc915276..27dd4f750a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1835,7 +1835,7 @@
Use this profile only for making Spark releases. Note that due to SPARK-8819,
you must use maven version 3.2.x or before to avoid running into MSHADE-148.
-->
- <id>release-profile</id>
+ <id>release</id>
<properties>
<!--
The maven shade plugin has a bug where enabling the `createDependencyReducedPom`