GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/2016
[ZEPPELIN-2105] yarn installed by frontend-maven-plugin causes build
failure (BUG)
### What is this PR for?
yarn installed by frontend-maven-plugin causes build failure **when there
is no nodeJS in local system**
To reproduce this bug
- Remove system nodejs
- Execute `mvn -X clean package -pl 'zeppelin-web' -DskipTests;`
#### Details.
- yarn installed by frontend-maven-plugin can't run commands described in
scripts tag (`package.json`)
- but npm is able to execute them.
- so, it's bug of the maven plugin.
#### See also
https://github.com/apache/zeppelin/pull/2002
https://github.com/eirslett/frontend-maven-plugin/issues/562
### What type of PR is it?
[Bug Fix]
### Todos
* [x] - Rollback yarn to npm
* [x] - Update README.md for zeppelin-web
### What is the Jira issue?
[ZEPPELIN-2105](https://issues.apache.org/jira/browse/ZEPPELIN-2105)
### How should this be tested?
- Remove system nodejs
- `mvn -X clean package -pl 'zeppelin-web' -DskipTests;`
### Screenshots (if appropriate)
NONE
### 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/1ambda/zeppelin
ZEPPELIN-2105/rollback-yarn-to-npm
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2016.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 #2016
----
commit 66543efa69044f9f01c76ade332371c9f5555e7d
Author: 1ambda <[email protected]>
Date: 2017-02-13T16:48:57Z
fix: Rollback yarn to npm
commit ed8c4ceaf7b90750eeaf355704eac0f971f926e2
Author: 1ambda <[email protected]>
Date: 2017-02-13T16:49:08Z
docs: Update README for zeppelin-web
----
---
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.
---
