That’s right. However , for completeness it is useful to list the products and their versions, as is done for products under other licenses. The NOTICE should contain only AL dependency NOTICE with the relevant section.
You can find this documented here https://infra.apache.org/licensing-howto.html I will create the PR to illustrate that. I have quite experience on these legal aspects. Regards JB Le lun. 9 mars 2026 à 11:18, Robbie Gemmell <[email protected]> a écrit : > > -- LICENSE IS NOT CORRECT. The war contains artifacts (in WEB-INF/lib > > folder) not documented in the license (like Jolokia, caffeine, etc). > > -- NOTICE IS NOT CORRECT, for the same reason as LICENSE (mentioning the > > non ASF dependencies/LICENSE). > > I dont believe these points are correct. Jolokia and Caffeine are both > ASLv2 licensed and so dont have specific license needing to be > mentioned in the LICENSE file, and are already covered by the main > ASLv2 there. The console is not shipping any of the agent or website > parts mentioned in the jolokia NOTICE file (bits which do include some > non ASLv2 bits), which would mean there is nothing to add to the > required NOTICEs for it either. Caffeine has no notices. > > Robbie > > On Sat, 7 Mar 2026 at 18:14, Jean-Baptiste Onofré <[email protected]> wrote: > > > > +1 (binding) > > > > I checked: > > - source distribution > > -- signature and checksum are good > > -- LICENSE is good. > > -- NOTICE is good. The copyright year should be 2026 (instead of 2025). I > > will submit a PR about that. > > -- Some files don't contain ASF header. That's not strictly required (as > > it's "documentation files" like README.md, but good to have). I will > create > > a PR about that too. > > -- No binary/compiled file in the source distribution > > - binary distribution > > -- signature and checksum are good > > -- LICENSE IS NOT CORRECT. The war contains artifacts (in WEB-INF/lib > > folder) not documented in the license (like Jolokia, caffeine, etc). > > -- NOTICE IS NOT CORRECT, for the same reason as LICENSE (mentioning the > > non ASF dependencies/LICENSE). > > > > I will create the corresponding PRs to fix the "legal" issues. As there > > are not new issues, I don't want to block this release, but we have to > fix > > that asap (legal). > > > > Regards > > JB > > > > On Fri, Mar 6, 2026 at 1:05 PM Andy Taylor <[email protected]> > wrote: > > > > > I would like to propose an Artemis Console 1.7.0 release. The main > > > focus of this release is for dependency upgrades and bug fixes > > > > > > The Binary artifacts can be found at > > > https://dist.apache.org/repos/dist/dev/artemis/artemis-console/1.7.0 > > > > > > The Maven staging repository is here: > > > hhttps:// > repository.apache.org/content/repositories/orgapacheartemis-1013 > > > < > https://repository.apache.org/content/repositories/orgapacheartemis-1013> > > > > > > If you would like to validate the release you can either: > > > > > > 1. Check out the source, build and follow the readme instructions > > > (README.md) to deploy and smoke test the console. > > > 2. Download the binary distribution and deploy in a web container. > > > 3. Replace the console war in the latest An Artemis release or a > > > build from source. > > > > > > [ ] +1 approve this release [ ] +0 no opinion [ ] -1 disapprove (and > > > reason why) > > > > > > Here's my +1 > > > > > > Andy Taylor > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
