Repository navigation
RC-352 Move sonar-server ruling project to the repository root - #18
Conversation
Code Review ✅ Approved 🟡 Medium risk 1 closed / 1 findingsMoving the 6.5 server fixture to sonar-server and changing its Maven parent path could break fixture builds or dependent ruling tests if path resolution differs. Moves the SonarQube 6.5 sonar-server ruling fixture to the repository root, with its Maven parent resolved from the repository and unused wrapper POMs, README, and ignore file removed. The previously open finding about the stale symbolic-execution fixture path was addressed in #19. No open issues remain. ✅ 1 closed✅ Cross-Repo: sonar-java-symbolic-execution ruling still points at the old fixture path
Verification Repos 2 inspected · PRs 3 inspectedFunctional validation No results Rules 1 not applicable Broader impact Repos 2 inspected PRs 3 inspectedCross-repo 2 repositories inspected 0 open impacts
Cross-PR 3 PRs inspected 0 open impacts
Auto-approval Not enabledFor more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
Summary
sonar-serverdirectory.Companion PRs
These consumers build
sonar-serverfrom this repository and must bumpits/sourcestogether with their ruling test update:JavaRulingTest.sonarqube_server(expected baselines are unchanged because its project key and module base directory stay the same).Merge this fixture PR first. Until their companion PRs merge, the consumers must keep their
its/sourcessubmodule pinned before this commit.Validation
git diff --check HEADpasses.Part of RC-352