Hi Colm, Thanks for this!
>> Kai, is there a reason that the zookeeper + nimbus dependencies are not in >> the lib directories of the distributions? This is a good question I happened to know the answer. Yes we have already supported various KDC back ends, like the LDAP, ZK ones, but which one is to bundle in the KDC dist and used by default? It's hard to tell, because each one seems to need some time to mature. I'd suggest we take time to improve them when received user interests. So that's why we didn't put all the supported back ends in the dist. Nimbus is another story, it's for the token support. It's not bundled by default because I'm not sure most users would want the token support. Considering this release trouble, now I intend we don't bundle this plugins that involve external deps heavily, but it's just a thought. We can discuss about the way later. For now less change much better. Thanks again. Regards, Kai -----Original Message----- From: Colm O hEigeartaigh [mailto:[email protected]] Sent: Tuesday, May 09, 2017 4:52 PM To: [email protected] Subject: Re: Questions about the release OK I have made some changes based on my understanding of what is required. Please correct me if I'm wrong! Mockito, Hamcrest (junit) are test dependencies and are not required in the NOTICE file or to specify the license. We bundle Netty and SLF4J in the distribution. So we have the SLF4J license included in "licenses" and mentioned in NOTICE, as well as the Netty NOTICE. From what I can see from kerby-dist/kdc-dist/target/lib and kerby-dist/tool-dist/target/lib, all of the dependencies are covered. However, in NOTICE we also have the "nimbus-jose-jwt," NOTICE and the "JLine" NOTICE (from Zookeeper). However, it appears we don't bundle either of these in the "lib" directories so I'm not sure why they are there. Kai, is there a reason that the zookeeper + nimbus dependencies are not in the lib directories of the distributions? Colm. On Tue, May 9, 2017 at 7:35 AM, Zheng, Kai <[email protected]> wrote: > Thanks Emmanuel and Colm! Could we lend your hands on this? Sure if > your bandwidth allows. We're much dummy in such things and seem to > have on confidence to get it right. :( > > For the long term, I would suggest we reorganize Kerby into two projects: > kerby-kerb for the Kerberos core and library; kerby-kdc. The two > projects can be separately released in their own appropriate cycles. > For Kerby-kerb, it avoids any 3rd party deps. > > Regards, > Kai > > -----Original Message----- > From: Emmanuel Lécharny [mailto:[email protected]] > Sent: Tuesday, May 09, 2017 7:17 AM > To: [email protected] > Subject: Re: Questions about the release > > > > Le 08/05/2017 à 21:40, Colm O hEigeartaigh a écrit : > > I don't think we need the Mockito notice as it's a test dependency, > right? > > right. > > -- > Emmanuel Lecharny > > Symas.com > directory.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
