Floci's Java package is moving to io.floci.aws

[hectorvent]

We are renaming Floci's Java package from io.github.hectorvent.floci to io.floci.aws, with Maven groupId io.floci. This brings floci-aws in line with the rest of the family (io.floci.gcp, io.floci.az, io.floci.oci, io.floci.cli). The final rename is planned for November 4 to 6. We will keep you informed here and in #6589, where progress is tracked.

If you run Floci

Almost nothing changes. The Docker image, the native binary, release assets, ports, FLOCI_* environment variables and your persisted data all stay the same. Existing state keeps loading after the upgrade, because nothing Floci stores records a Java class name.

The one thing to update is log level overrides, because log categories follow the package:

# before
quarkus.log.category."io.github.hectorvent.floci.services.sqs".level: TRACE
# after
quarkus.log.category."io.floci.aws.services.sqs".level: TRACE

The same applies to the environment-variable form: QUARKUS_LOG_CATEGORY__IO_GITHUB_HECTORVENT_FLOCI_SERVICES_SQS__LEVEL becomes QUARKUS_LOG_CATEGORY__IO_FLOCI_AWS_SERVICES_SQS__LEVEL. The release notes for the version that includes the rename will call this out again.

If you contribute

The rename lands as a single mechanical PR. Small prep PRs go in first, so the final change touches little beyond package and import lines and the file moves:

• chore: add the package rename tool (report and apply) #6556 (merged) adds tools/rename/rename_package.py, which performs the rename and reports what is left to clean up.
• chore: derive class-name strings in main from the class #6588 and chore(ci): start Checkstyle suppression paths below the package root #6584 remove class names written as strings and make the Checkstyle suppressions independent of the package.
• Next come a few PRs that replace inline fully qualified names with imports, one area at a time.

Your open PR does not need to wait for any of this. The final PR is planned for November 4 to 6. When it merges, we will post a short recipe here that replays the rename on your branch, so you will not have to resolve the import conflicts by hand. We will confirm the exact day here and in #6589 as it gets closer.

Questions or concerns are welcome in this thread.