GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/2232
[ZEPPELIN-2373] Remove -Pyarn build profile
### What is this PR for?
Currently users who build Zeppelin from source need to include `-Pyarn`
build profile to enable Yarn for embedded local Spark. This PR is to remove
`-Pyarn` and make Yarn related libraries can be automatically downloaded
without the profile during build time.
### What type of PR is it?
just removed Yarn build profile in `spark-dependencies/pom.xml`
### What is the Jira issue?
[ZEPPELIN-2373](https://issues.apache.org/jira/browse/ZEPPELIN-2373)
### How should this be tested?
1. apply this patch and build Zeppelin with below command
```
mvn clean package -DskipTests -pl 'zeppelin-server, spark-dependencies,
spark' --am
```
2. check `spark-yarn_${scala.binary.version}.jar` is downloaded(or
included) during build time
```
[INFO] Including org.apache.spark:spark-yarn_2.10:jar:2.1.0 in the shaded
jar.
```
In current master, the above line won't be shown if you don't use `-Pyarn`
build profile. But with this patch, it will be shown without the profile.
### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/zeppelin
ZEPPELIN-2373/includeYarnByDefault
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2232.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2232
----
commit 59eb2b505ff1ca70ff31cd3aaf1a7b3b5998e09a
Author: AhyoungRyu <[email protected]>
Date: 2017-04-07T10:44:26Z
Remove -Pyarn build profile
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
