ci: update site descriptor to 2.0.0

[jy95]

Summary by CodeRabbit

• Chores
  • Standardized XML configuration file structure and namespace formatting across project modules for consistency.

[coderabbitai]

Walkthrough

Four Maven Site XML descriptor files are updated to standardize their format: the root element changes from <project> to <site> with proper namespace declarations, an XML declaration is added, and bannerLeft elements are converted from nested structures to self-closing elements with attributes.

Changes

Cohort / File(s)	Summary
Maven Site XML standardization common/src/site/site.xml, r4/src/site/site.xml, r5/src/site/site.xml, src/site/site.xml	Root element changed from <project> to <site> with XML declaration and namespace attributes (xmlns, xmlns:xsi, xsi:schemaLocation). bannerLeft element refactored from multi-line nested structure with child <name> and <href> elements to self-closing element with name and href attributes. Closing tag updated from </project> to </site>.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• These are consistent, homogeneous schema updates applied identically across 4 files
• Pattern repetition across files reduces individual reasoning needed per file
• Changes are straightforward XML structural transformations with no logic implications

Poem

🐰 Four sites were dressed in newfangled schema,
With banners transformed from branch to attribute—
Our XML now speaks the language of Maven,
Standardized, clean, and wonderfully mute.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating site descriptor files to a new format (2.0.0), which is reflected across all four modified site.xml files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch updateSite

---

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 and usage tips.}

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00% (target: -1.00%)	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (f7f6c69)	1487	1483	99.73%
Head commit (6ec3dbb)	2974 (+1487)	2966 (+1483)	99.73% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#245)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f840fad and 6ec3dbb.

📒 Files selected for processing (4)

• common/src/site/site.xml (2 hunks)
• r4/src/site/site.xml (2 hunks)
• r5/src/site/site.xml (2 hunks)
• src/site/site.xml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Analyze (java-kotlin)
• GitHub Check: submit-pypi

🔇 Additional comments (3)

src/site/site.xml (1)

1-6: Consistent standardization across root and bannerLeft transformations.

This file follows the same Maven Site 2.0.0 migration pattern as the common site descriptor, maintaining consistency across the project.

Also applies to: 11-11

r5/src/site/site.xml (1)

1-2: XML declaration correctly specifies UTF-8 for Unicode support.

The UTF-8 encoding declaration properly supports the emoji characters used in the menu labels (lines 14-26).

r4/src/site/site.xml (1)

1-6: Completes consistent Maven Site 2.0.0 standardization across all site descriptors.

All four site descriptor files (common, root, r4, r5) now follow the identical namespace and element transformation pattern for Maven Site 2.0.0 compatibility.

Also applies to: 11-11