[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.
This commit is contained in:
parent
5c080c2ee4
commit
397bafd7db
|
@ -118,13 +118,13 @@ if [[ ! "$@" =~ --skip-publish ]]; then
|
|||
|
||||
rm -rf $SPARK_REPO
|
||||
|
||||
build/mvn -DskipTests -Pyarn -Phive -Prelease-profile\
|
||||
build/mvn -DskipTests -Pyarn -Phive -Prelease\
|
||||
-Phive-thriftserver -Phadoop-2.2 -Pspark-ganglia-lgpl -Pkinesis-asl \
|
||||
clean install
|
||||
|
||||
./dev/change-version-to-2.11.sh
|
||||
|
||||
build/mvn -DskipTests -Pyarn -Phive -Prelease-profile\
|
||||
build/mvn -DskipTests -Pyarn -Phive -Prelease\
|
||||
-Dscala-2.11 -Phadoop-2.2 -Pspark-ganglia-lgpl -Pkinesis-asl \
|
||||
clean install
|
||||
|
||||
|
|
2
pom.xml
2
pom.xml
|
@ -1821,7 +1821,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`
|
||||
|
|
Loading…
Reference in a new issue