I've created https://issues.apache.org/jira/browse/ZEPPELIN-4433 to perform one time update of the helium registry & https://issues.apache.org/jira/browse/ZEPPELIN-4434 for setting up automated process for keeping it up to date.
On Sun, Nov 3, 2019 at 4:43 PM moon soo Lee <[email protected]> wrote: > cc ahyoung. Could you take a look?? And, any good idea how we can we move > helium.json and related code zeppelin project source tree? > > > On Sun, Nov 3, 2019 at 06:01 Jeff Zhang <[email protected]> wrote: > > > + Moon > > > > I think helium.json on S3 is maintained by ZEPL, Moon should know the > > details. > > > > > > Alex Ott <[email protected]> 于2019年11月3日周日 下午6:52写道： > > > > > Hi all > > > > > > I've noticed that Helium registry ( > > > https://s3.amazonaws.com/helium-package/helium.json) is still listing > > > zeppelin-leaflet 1.0.4 as the latest, although 1.0.5 was released 5 > > months > > > ago (https://www.npmjs.com/package/zeppelin-leaflet) with some > > > improvements > > > regarding omitting the points that have null value for one of the > > > coordinates. > > > > > > As I understood from documentation, registry should be regenerated > > > automatically on publish of the new versions, but this doesn't happen. > > > > > > How we can enforce it? > > > > > > -- > > > With best wishes, Alex Ott > > > http://alexott.net/ > > > Twitter: alexott_en (English), alexott (Russian) > > > > > > > > > -- > > Best Regards > > > > Jeff Zhang > > > -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian)
