bobbai00 opened a new pull request, #4447: URL: https://github.com/apache/texera/pull/4447
### What changes were proposed in this PR? Every module's `build.sbt` was declaring `organization := "org.apache"` locally — the root `build.sbt` plus 11 per-module `build.sbt` files. That is not the correct groupId for an Apache top-level project; each TLP uses `org.apache.<project>`. This PR fixes the groupId to `org.apache.texera`. Mechanical change: - Add `ThisBuild / organization := "org.apache.texera"` at the top of root `build.sbt`. `ThisBuild` makes the setting apply to every subproject by default. - Remove `organization := "org.apache"` from all 11 per-module `build.sbt` files, and from the root `TexeraProject` aggregator settings block. Net diff: 13 files, +2 insertions, -15 deletions. After this change, `sbt dist` produces jars named `org.apache.texera.<artifact>-<version>.jar` and the Maven coordinates are `org.apache.texera:<artifact>:<version>`. ### Any related issues, documentation, discussions? Closes #4446. Note: a follow-up change is needed in `bin/licensing/check_binary_deps.py` to teach the license checker to skip jars whose groupId starts with `org.apache.texera.` (otherwise the new `check-binary-licenses.yml` CI job will continue to flag Texera's own jars as unclaimed third-party dependencies). That follow-up is intentionally out of scope for this PR to keep the diff minimal. ### How was this PR tested? - Verified `grep -rn '^organization' --include='*.sbt' .` returns no matches after the change. - Verified `git diff origin/main --stat` shows only the 13 expected files, +2/-15. - `sbt 'reload; projects'` to confirm every subproject loads under the new groupId. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 4.7) -- 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]
