Thanks for your reply. It’s also my understanding and what I applied initially.
I’m doing the changes. Thanks ! Regards JB Le dim. 11 mai 2025 à 12:02, Justin Mclean <jus...@classsoftware.com> a écrit : > Hi, > > > Do you think what's provided in > > https://issues.apache.org/jira/browse/LEGAL-684 is accurate/complete ? > > Yes, and it follows the advice in [1] > > > Specifically, as the how-to states: "Do not add anything to NOTICE > > which is not legally required." So, if those dependencies have > > third-party notices in NOTICE, then those third-party notices must be > > included in this new NOTICE as well. > > That is correct (well, it's what's bundled in the release, not all its > dependencies). > > > For cases where we are including whole products within another > > product, it makes sense to include the whole copyright notices for > > those products along with their third-party notices. > > Yes. So, for example, you’ll need to do this with Picocli. > > > For cases like > > this, where the project is deriving code from another ASF project, as > > opposed to including the other project, it is not appropriate to > > include the full copyright statements in NOTICE since it does not help > > the recipients to know this information. > > Which is fine, but remember copyright lines end up in NOTICE files for > several reasons other than just the ASF copyright line: > a) Those that are relocated as their header have been removed from files. > b) Because of a software grant. > c) Because they were in other 3rd party NOTICE files and copied from those. > > > Can you clarify ? If your "personal" preference is to have all NOTICE > > and all content (including for ASF dependencies) > > No, that's not my preference. You need to include only what is needed. > Each ASF NOTICE still needs to be looked at to see what needs to be > included, as it may contain other notices. > > Kind Regards, > Justin > > 1. https://infra.apache.org/licensing-howto.html
