Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2089
@felixcheung Could you review my PR?
---
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 DmytroShkvyra reopened a pull request:
https://github.com/apache/zeppelin/pull/2089
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions under
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2089
---
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
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2089
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions under
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2075
add wildcard
---
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
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2075
---
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
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2075
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2032
---
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
GitHub user DmytroShkvyra reopened a pull request:
https://github.com/apache/zeppelin/pull/2032
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2032
---
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
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2032
---
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
GitHub user DmytroShkvyra reopened a pull request:
https://github.com/apache/zeppelin/pull/2032
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2032
Failed tests:
NotebookTest.testPublicPrivateNewNote:1173 expected:<2C9[FXZKX8]> but
was:<2C9[4VAUTF]>
NotebookTest.testAuthorizationRoles:759 expected: but was:
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2032
Seems to Jenkins does not work properly. See Travis results below:
https://travis-ci.org/DmytroShkvyra/zeppelin/builds/203390388
---
If your project is set up for it, you can reply
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2032
[ZEPPELIN-791] add wildcards
What is this PR for?
It is better have a single place where we manage project-wise RAT
exclusions for a contributions under licenses different from
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2027
---
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
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2027
[ZEPPELIN-791] Build infra: move all RAT to root pom.xml
### What is this PR for?
Is is better have a single place where we manage project-wise RAT
exclusions for a contributions under
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Incompatible with https://github.com/apache/zeppelin/pull/2016
---
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 DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2002
---
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
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul May be make sense just create PR only for try moving to JDK8 and
test this with Travis? Anyway nobody will not merge it to zeppelin without
approve.
---
If your project is set
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul Should I close ZEPPELIN-411 as "wont fix"?
---
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 pr
Github user DmytroShkvyra closed the pull request at:
https://github.com/apache/zeppelin/pull/2024
---
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
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Installation of hidden dependencies was removed. (accordingly to reviewers
comments).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>Could you share the content of
/vagrant/zeppelin/local-repo/helium-bundle/npm-debug.log? when node/node
node_modules/webpack/bin/webpack.js --display-error-details --j
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Failed tests:
IgniteSqlInterpreterTest.testSql:95 expected: but was:
This test do not related with PR.
---
If your project is set up for it, you can reply to this email and have
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
> I think we don't need to worry about max call stack size since it
occurs in unusual env like windows, linux on vm.
> Zeppelin is not the thing li
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda BTW I have reverted my changes in README.md for build and test from
CL and add section about build and test with maven like this example:
```
mvn test -Dmaven.clean.skip=true
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda No, I want make "normal|classical" maven project which do not need
preinstall everybody nodejs and their packages by hand. More over - yarn works
faster than npm
-
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda Yes, this different from build, but cause the same. Helium
installed npm with frondend-maven-plugin.
BTW. Many contributors cant use windows because this is proprietary
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda I repeat again (very slowly):
1. We cant install npm with frontend-maven-plugin locally. It throws a lot
of errors like this (zeppelin.log) this is attempt install npm
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>That's cool. You are trying to modify something without understanding.
Anyway, We have 2 problems.
> local development
> you must install yarn if you wa
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda
>If you want to use node modules in terminal, you have to install them
globally. (e.g $ yarn install)
>But in case of grunt (and karma so on..), we don't need
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
Hi @Leemoonsoo, fontconfig only need to run pahantomjs browser during test
phase of maven build. If you don't want run tests and install fontconfig you
can pass -DSkip.test option to maven
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
All these packages are required and used in scripts of package.json. I
have tested this (run mvn build at clean vbox). And when I tried run
$ npm install -g yarn
$ yarn install
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2002
@1ambda Seems to Ignite and MR filed. They not related to zeppelin-web.
Is problem in proxy-configuration for bower? I could add support for this
in POM.xml via -D parameters. But I
GitHub user DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/2002
[ZEPPELIN-1928]: Get a rid of preinstalled external dependencies (nodejs
and npm) for maven build
### What is this PR for?
Get a rid of preinstalled external dependencies (nodejs
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/1961
@jongyoul Yes, you can do this like described there
https://issues.apache.org/jira/browse/MASSEMBLY-781?focusedCommentId=14640499=com.atlassian.jira.plugin.system.issuetabpanels:comment
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/1961
@felixcheung Done. I hope that new title is more precise than previous.
---
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 DmytroShkvyra opened a pull request:
https://github.com/apache/zeppelin/pull/1961
[ZEPPELIN-1934] Building from source documentation
### What is this PR for?
maven-assembly-plugin fails make-assembly execution when the executing
user's ID is "too big."
39 matches
Mail list logo
