[jira] [Created] (BIGTOP-2514) Update Zeppelin version to 0.6.1

Alexander Bezzubov created BIGTOP-2514: -- Summary: Update Zeppelin version to 0.6.1 Key: BIGTOP-2514 URL: https://issues.apache.org/jira/browse/BIGTOP-2514 Project: Bigtop Issue Type:

Re: [DISCUSS] Unblocking Juju development

Now my time to be late with a replay, but the good news -- I'm back from vacation! :-) On Tue, Aug 2, 2016 at 12:09 PM, Konstantin Boudnik wrote: > Sorry for the belated joining of the party - crazy travel schedule an all > that. I like the idea of making a special branch for

[GitHub] bigtop issue #44: BIGTOP-1769. Zeppelin Integration

Github user c0s commented on the issue: https://github.com/apache/bigtop/pull/44 I guess... --- 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] bigtop issue #44: BIGTOP-1769. Zeppelin Integration

Github user bzz commented on the issue: https://github.com/apache/bigtop/pull/44 Shall this one be closed, as soon as [BIGTOP-1769](https://issues.apache.org/jira/browse/BIGTOP-1769) is resolved? --- If your project is set up for it, you can reply to this email and have your reply

Re: builds.apache.org

The point there is that only builds done on builds.apache.org are capable of pushing nightly artifacts to official ASF Maven repo for snapshots. Given the restructuring of the build systems -- somebody has to probably update those jobs to still be relevant. Thanks, Roman. On Mon, Aug 8, 2016 at

Re: builds.apache.org

On Mon, Aug 08, 2016 at 08:52PM, Olaf Flebbe wrote: > Hi Cos, > > thanks for jumping in. > > I am failing to understand the maven repository things involved here. > > For instance It seems to me that the version in pom.xml are horrible out of > sync with bigtop.bom. > Reading BIGTOP-1429 I have

Re: builds.apache.org

Hi Cos, thanks for jumping in. I am failing to understand the maven repository things involved here. For instance It seems to me that the version in pom.xml are horrible out of sync with bigtop.bom. Reading BIGTOP-1429 I have got the impression that we technically cannot run the mvn deploy

Re: builds.apache.org

On Mon, Aug 08, 2016 at 02:07AM, Evans Ye wrote: > Except for Bigtop-trunk, which we're building the whole set of rpm/deb for > OS matrix, I've no idea what others are doing. > Maybe Roman knows better. > > 2016-08-07 3:22 GMT+08:00 Olaf Flebbe : > > > Hi, > > > > can anyone

Re: builds.apache.org

Hi Evans, Using my PMC Chairs Karma I added you to the jenkins admins for build.apache.org Please see at the jobs yourself: https://builds.apache.org/view/B/view/Bigtop/ For instance The bigtop-trunk job does a mvn deploy with a JDK 1.6 . We either can remove this altogether or should update

[jira] [Created] (BIGTOP-2513) Some RAT exclude rules defined in build.gradle are not defined in pom.xml

Kengo Seki created BIGTOP-2513: -- Summary: Some RAT exclude rules defined in build.gradle are not defined in pom.xml Key: BIGTOP-2513 URL: https://issues.apache.org/jira/browse/BIGTOP-2513 Project:

[jira] [Created] (BIGTOP-2512) Wrong help message in docker-hadoop.sh

Kengo Seki created BIGTOP-2512: -- Summary: Wrong help message in docker-hadoop.sh Key: BIGTOP-2512 URL: https://issues.apache.org/jira/browse/BIGTOP-2512 Project: Bigtop Issue Type: Bug