I think documenting this would be useful for someone who want to try helium proposal ( https://cwiki.apache.org/confluence/display/ZEPPELIN/Helium+proposal)
Jars are from public central repository or from the local repository. https://github.com/Leemoonsoo/incubator-zeppelin/blob/helium/zeppelin-interpreter/src/main/java/org/apache/zeppelin/dep/DependencyResolver.java#L61 is how it setup the repositories. It's PoC implementation so no convenient features like adding remote repo from configuration, yet. But you can always modify the source code. On Wed, Nov 4, 2015 at 12:50 AM tog <[email protected]> wrote: > Thanks for the quick feedback ... > I copied the spec files already but stupidly completely forgot to push the > jars in my local maven. How is the jar resolution done - can I choose a > remote maven repo ? > > Would a documentation be useful? Then any idea where to put it at this > stage? > > Cheers > Guillaume > > On 3 November 2015 at 15:40, moon soo Lee <[email protected]> wrote: > >> Thanks for the interest to Helium! >> conf/helium.json is automatically generated. so you'll not need to create >> it. >> However, you'll need to write helium/[app].spec files. (which planning to >> automatically downloaded from some package registry homepage, in the future) >> You can find this file from example. >> >> https://github.com/Leemoonsoo/zeppelin-wordcloud/blob/master/wordcloud.spec >> >> To try, you'll need install these examples in your local .m2 repository >> (using mvn install) and copy *.spec file into ZEPPELIN_HOME/helium/ >> directory. >> >> Thanks, >> moon >> >> On Wed, Nov 4, 2015 at 12:33 AM tog <[email protected]> wrote: >> >>> Hi >>> >>> I played a bit with Helium and unfortunately was not able to fully >>> configure it. Would someone have gone through it as well and share what >>> should go in helium.json >>> >>> Cheers >>> Guillaume >>> >> > > > -- > PGP KeyID: 2048R/EA31CFC9 subkeys.pgp.net >
