I've posted this question in the gradle forums, specifically directed at hopefully to bump gradle upstream packaging up as a first class priority, so that it will be easier for all of us to adopt bigtop at a broader level in the downstream.
If any of you know people in the gradle community, maybe we can try to work with them , or discuss with them, about possibilities for making gradle a first class linux tool.
In the end it will increase bigtop adoption if its core toolchain has unambiguous licensing ans is easy to package.
Any other thoughts about the elephant in the room (gradle is awesome and fun to use, but also its new to enterprises and they arent comfortable with its packaging yet), and how we can improve the situation?Or any of you folks know anyone in the gradle community we can work with on this?
It'd be certainly great to have this technology packages as a part of any standard linux distro. It isn't like Bigtop is blocked by the absense of such packaging, but having it in place won't hurt for sure.
Thanks will ! I guess for now its not a huge concern: BigTop will still ship and work just fine. And since most of the bigtop sources are in groovy and java anyways, the core stuff can be used in a variety of different ways. On Wed, Apr 30, 2014 at 9:31 PM, Will Benton <[EMAIL PROTECTED]> wrote: Jay Vyas http://jayunit100.blogspot.com
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation project and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext