Yes, right. BTW, I think we need to make dependencies clearly between zeppelin-server and interpreters, and even among interpreters. Some versions properties are used in zeppelin-server and interpreters, but no one has any clear view for them. So I thought it would be a change when we divide repositories. The second one is about building and compiling. We don't have to build Zeppelin fully when building some components. We also can do it with custom build options including '-pl !...'. I don't think it's good and there's no reason to keep this kind of inconvenience. What do you think?
Regards, JL On Wed, Dec 12, 2018 at 3:08 PM Jeff Zhang <zjf...@gmail.com> wrote: > Hi Jongyoul, > > Thanks for bring this up. I don't understand how different repo will help > here, but I thought about moving interpreters out of zeppelin for a long > time, but don't have bandwidth for it. The release cycle of zeppelin core > component (zeppelin-zengine, zeppelin-server) should not block the release > of interpreter component (unless they depends on some features of > zeppelin-zengine, zeppelin-server). > > > Jongyoul Lee <jongy...@gmail.com> 于2018年12月12日周三 上午10:38写道： > > > Hi, dev and committers, > > > > Currently, I'm seeing the repositories of another apache projects. They > > have some several repositories with different purposes. I'd like to > suggest > > you that we divide repositories between zeppelin-server and others. > > > > This will help you develop zeppelin-server without interfering from other > > components and its dependencies. Even, in the case of interpreters, It > will > > provide more independent environments for developing interpreters > > themselves. Currently, we had a lot of dependencies and various versions > > for each interpreter. > > > > WDYT? > > > > Regards, > > JL > > > > -- > > 이종열, Jongyoul Lee, 李宗烈 > > http://madeng.net > > > > > -- > Best Regards > > Jeff Zhang > -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net
