Github user shijinkui closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/905
---
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
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-222162047
I agree with @bzz. If your PR has both of parts which change behavior or
not, I suggest you divide two seperate PR because of easy review. If you mix
them,
GitHub user shijinkui reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/905
[ZEPPELIN-870] Improvement build and pom normalized
### What is this PR for?
1. frontend-maven-plugin upgrade to 1.0, as low version occur error when
build on osx
2. upgrade
Github user shijinkui closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/905
---
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
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-222056071
@shijinkui Just close and reopen it. :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-222055896
@jongyoul I have no authorizationã cc @bzz
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jongyoul commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221920236
@shijinkui It becomes green. Could you please trigger it again?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221823115
@bzz have rebased. Failed all for the spark archive download timeout by
the url
`http://archive.apache.org/dist/spark/spark-1.6.1/spark-1.6.1-bin-without-
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221797699
As #862 is merged - it should fix the CI, so could you please rebase on the
latest master and see if that helps?
---
If your project is set up for it, you can r
Github user bzz commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221793621
@shijinkui I do not think that mentioned fronted build warnings are
relevant to CI build failure.
It seems that Selenium integration tests are failing
Github user shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221578790
hi, @bzz the bower error, my local compile is ok, how can i continue
```
[ERROR] bower angular-ui-ace#0.1.1invalid-meta angular-ui-ace i
Github user shijinkui commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/905#issuecomment-221204936
hi, @bzz thanks for review. had add spark-1.6 default active and validate
phrase.
For the changes not more enough to separate, I think in one pr may b
12 matches
Mail list logo
