ci: Replace CodeQL autobuild with explicit Maven compile#102
Conversation
…epos autobuild downloads Maven 3.8.8 which fails because git-commit-id-maven-plugin 10.0.0 requires Maven [3.9.0,). The other three repos (java-llama.cpp, BAF, llamacpp-ai-index-maven-plugin) already use an explicit mvn compile step that uses the system Maven installed by setup-java. Synchronize streambuffer. https://claude.ai/code/session_01FGnfLjjGbiZxknfbUnnwUr
Review Summary✅ Approved — This is a low-risk, well-motivated CI improvement. What's Good
No Concerns
Recommendation: ✅ Ready to merge. |
Error Prone flags [NotJavadoc] when two /** */ blocks appear on the same element; -Werror turns it into a build failure on CodeQL. Remove the first (shorter, incomplete) block — the second is the canonical one with all @param and @return tags. https://claude.ai/code/session_01FGnfLjjGbiZxknfbUnnwUr
|
Review Summary✅ Approved — Two focused, well-motivated changes: CI/Build Improvement (CodeQL workflow)
Javadoc Cleanup
Overall Assessment
|



Summary
autobuildaction with an explicitmvn --batch-mode compilestep in the CodeQL workflowTest plan
Related issues / PRs
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdSECURITY.md)https://claude.ai/code/session_01FGnfLjjGbiZxknfbUnnwUr