Move checkstyle cache to project root directory

[wendigo]

Airbase contribution check list

• Git commit messages follow https://cbea.ms/git-commit/.
• All automated tests are passing.
• Pull request was categorized using one of the existing labels.

[wendigo]

This makes subsequent Trino builds faster (even when cleaned):

After:

[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:15 min (Wall Clock)
[INFO] Finished at: 2026-08-26T16:24:39+02:00
[INFO] ------------------------------------------------------------------------

Before:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  02:00 min (Wall Clock)
[INFO] Finished at: 2026-08-26T16:28:15+02:00
[INFO] ------------------------------------------------------------------------

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e0fa9bf8-025b-4d77-b464-73773db415eb

📥 Commits

Reviewing files that changed from the base of the PR and between c187f9d and 5611aec.

📒 Files selected for processing (2)

• .gitignore
• airbase/pom.xml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Maven configuration adds a version-keyed Checkstyle cache path and assigns it to the maven-checkstyle-plugin through cacheFile. The .gitignore file ignores .checkstyle-cache/ directories.

Merge Risk: ⚪ Minimal · up to 5611a

The change moves the Checkstyle cache into a version-keyed project-root directory and ignores it from source control; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 89836248-39aa-4f90-aebe-e9992a2cab40

📥 Commits

Reviewing files that changed from the base of the PR and between 0294a56 and c187f9d.

📒 Files selected for processing (1)

• airbase/pom.xml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

[wendigo]

[findepi]

I like quicker builds. And I very much dislike how much time checkstyle takes on a clean (Trino) biuld.
But i also like the fact that "clean && build" is "a clean build", from well defined state. It could be very confusing if someone couldn't reproduce a CI failure despite running ./mvnw clean first.

I know the problem is pre-existing because of .node and node_modules directories, but I am not convinced the gain is worth the added complexity.

Maybe we should hear others opinion before merging?

[wendigo]

Why would I need to "reproduce CI failure" around checkstyle?