Thanks Emmanuel. Do you mean if we don't bundle the dependency jars in the released package, the N&L are not needed? If so, I think we can just release the source code for has-dist, users can download the source code, compile it before use it. Because the dependencies will change after upgrading the version, that will increase our maintenance cost. Please correct me if I am wrong.
Thanks, Jiajia -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Thursday, October 11, 2018 4:20 PM To: [email protected] Subject: Re: Kerby 2.0.0 Le 11/10/2018 à 08:12, Li, Jiajia a écrit : > Hi Colm, > > I have added the NOTICE, LICENSE and README, but I have one question, > has-server with the hadoop-common(Apache license) dependency, so all the > hadoop-common dependency jars will be under the target/lib folder, should we > add N&L for these jars? You should include all the N&L of all the dependencies you are bundling in the released package, including transitive dependencies (ie dependencies used by the dependencies...) This is painful, but required. You can use mvn dependency:tree for that purpose. Note that the N&L will change between a binary package and a source package. Typically, in a source package, if you have dependencies that are only added while building a binary package, then there is no need to add them (I'm thinking of installer libraries, for instance). -- Emmanuel Lecharny Symas.com directory.apache.org
