adityamparikh commented on PR #138: URL: https://github.com/apache/solr-mcp/pull/138#issuecomment-4684447342
For anyone reviewing — where the generated files land, and how to look at them: **In the artifacts.** The binary `LICENSE`/`NOTICE` are bundled in the executable JAR at `META-INF/LICENSE` and `META-INF/NOTICE`, so they're also inside every Docker image (the Jib JVM image and the native images all package the bootJar). You can pull them straight out of any built artifact: ```bash unzip -p build/libs/solr-mcp-<version>.jar META-INF/LICENSE unzip -p build/libs/solr-mcp-<version>.jar META-INF/NOTICE ``` After any `./gradlew build` they're also written to `build/generated/license/` for easy viewing (or run just `./gradlew generateBinaryLicense generateBinaryNotice`). The source-form jars — the thin `jar`, `-sources`, `-javadoc` — keep the plain repo-root `LICENSE`/`NOTICE`. **How they're built.** `LICENSE` is the Apache-2.0 text followed by an appendix that lists every bundled runtime dependency with a link to its license, taken from the CycloneDX SBOM (so it covers everything, including SolrJ/solr-api that the POM-based scanners miss). `NOTICE` is our own `NOTICE` plus the dependencies' `META-INF/NOTICE` files lifted verbatim and de-duplicated. It's a small `buildSrc` plugin, regenerated on every build, and the build fails if a bundled dependency isn't covered by the SBOM so nothing can ship unlisted. **Docs.** There's a new "Licensing & Notices" page for the MCP site that walks through all of this — where the files live, how to build them, how they're constructed, and the SBOM's role. It'll publish at `solr.apache.org/mcp/licensing.html`; the content + nav are in apache/solr-mcp#143 and apache/solr-site#175, and you can read the source markdown in #143 at `docs/site/content/pages/mcp/licensing.md`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
