GitHub user 1ambda reopened a pull request:

    https://github.com/apache/zeppelin/pull/1659

    [ZEPPELIN-1667] Fix maven options while updating node, npm packages

    ### What is this PR for?
    
    Update maven plugin, node vesion, npm package and fix tests to make #1639 
pass CI
    
    ### What is the Jira issue?
    
    Sub issue of #1639 
    
    ### Questions:
    
    Does the licenses files need update? NO
    Is there breaking changes for older versions? YES (front-end build tool 
usage changed)
    Does this needs documentation? YES (front-end build tool usage changed)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/1ambda/zeppelin pr/1639

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1659.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 #1659
    
----
commit 314dcd8b45f795fef987650ffc9d6b3cd42378b7
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T07:47:42Z

    chore: Update frontend plugin version

commit 6568960571a908854f07cc6ad4cd13982ade5e8d
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T08:05:21Z

    chore: Add test, build task to npm

commit 532f1e697ba3f7614e444b9d2e9a28f3bcd17177
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T12:37:26Z

    fix(web): npm tasks in pom.xml

commit f42531aff8ba5bad601bd40ea91be39f80d5bfa6
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:21:57Z

    chore: Update assembly plugin version

commit 668a68761b1c5f48568bcddc2cffc04527a901f5
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:24:43Z

    chore: Set maven option using mavenrc

commit 488092af94982d3da51cb1132fbab761311cc1ad
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:27:53Z

    chore: fix travis maven option

commit e08580983f0b6b4c04f7e2a485510ae7115bc78e
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:38:10Z

    chore: Remove bower install root option

commit 4c26211faec7822cc3b25d47dc4b53dc739ac737
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:44:55Z

    chore: Update node, npm version to avoid proxy error

commit ca2359c5226ea25491a898d8f9b3067dbdd0bce3
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T13:50:53Z

    fix: Restore bower install option

commit 6bb52ccace7617344033c99569464e709cd4da23
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T14:19:13Z

    chore: Add slient option to bower (show error only)

commit ded1f2c0dc8dfeb8224a71facdc18e9d5f64ad2b
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T14:31:40Z

    chore: Update karma, phantom related package version

commit ac40b5690d755f52914a9cc7d68139ddbec27a71
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-19T14:58:43Z

    test: fix test for jasmine-core 2.x
    
    ref - 
http://stackoverflow.com/questions/27680933/jasmine-have-createspy-return-mock-object

commit 5e1e746d5b324189f4e2b9e66dc5d8f8fa074bfd
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-21T02:42:36Z

    fix: Caching npm, bower, node directories

commit 5cdd813e1570638e290457e7c03ea373741d5c8c
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-21T03:05:53Z

    fix: Print warn, error log only while packing

commit a2aab1f22b89b6a4a407f5d4cd155bc0a9e1860d
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-21T03:07:28Z

    fix: Remove useless script

commit f0fcdff352e3fc6be4a6801c40d1de4a2bb99a66
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-22T04:37:11Z

    feat: Add start script to package.json

commit d8c9d36e777e278b4e2f8c94ece0ffabfff30d4b
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-22T04:37:34Z

    docs: Update zeppelin-web/README.md

commit e5b414b91a630fb8ea33ea1a8c59f3666a910dc6
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-22T04:49:04Z

    docs: Add a package installation command

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to