Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
Sorry maybe it's my mistake to set jira version.
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@corneadoug This PR shouldn't be merged to branch-0.6. Could you revert
related [commit](db7c11d3b62a8066b0138fd9700731c953cec1a5) from branch-0.6 ?
---
If your project is set up for it, you
Github user mikhaildubkov commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim i guess it would be better just replace
ZeppelinDevServer.DEFAULT_TEST_INTERPRETER_PORT by its int value for branch-0.6
to avoid necessary change for project build.
---
If your
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@mikhaildubkov `dev` doesn't exists on 0.6.x so you should use `master`
branch for this.
Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mikhaildubkov commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim ,
Once I checkout branch-0,6 I'm unable to build project due to compilation
error:
[ERROR] Failed to execute goal
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
Thank you @corneadoug
---
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
Github user corneadoug commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim You ping, I merge :)
---
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
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
ping
---
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 bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1358
Looks great to me!
Merging to master if there is no further discussion.
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim I rebuild with `mvn clean package -DskipTests -Pexamples` and it
works. I should've attached `-Pexamples`. Now I can see the Helium icon :)
Anyway I checked
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1358
I think it's not an issue related with this PR but Helium itself.
---
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
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@AhyoungRyu Thank you for reviewing!!
Did you clear your browser cache?
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1358
@astroshim Definitely in the latest master branch, I faced the below
exception when I tried to run
`org.apache.zeppelin.interpreter.dev.ZeppelinApplicationDevServer` in my IDE.
```
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1358
re-trigger CI
---
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,
14 matches
Mail list logo
