Use double quotes in Gradle files

[mernst]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request standardizes string quoting in Gradle build files: single-quoted literals were converted to double-quoted literals across build.gradle and gradle/mavencentral.gradle. Groovy property access was standardized (map-style getters), and POM/publication metadata (group, version, packageName, name, description, licenses, developers, repository URLs, and credentials access) were updated to use double quotes. No control flow, dependencies, build logic, or public API behavior was changed.

Pre-merge checks and finishing touches

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 21fbd35 and b200149.

📒 Files selected for processing (1)

• build.gradle (6 hunks)

🔇 Additional comments (3)

build.gradle (3)

222-222: Shell command correctly uses single quotes to avoid escaping issues.

The implementation properly handles nested quoting by retaining single quotes around '*.java' within the double-quoted shell command string. This avoids the need to escape inner double quotes and is the correct approach for this pattern.

---

1-223: Comprehensive quote conversion appears mechanically sound.

All single-quoted string literals throughout the file have been consistently converted to double-quoted strings. Across plugin declarations, version strings, URLs, file paths, and configuration parameters, the conversions maintain semantic equivalence since none of these strings use Groovy's string interpolation features ${...} and no special escaping differences apply to the literal values.

---

161-162: The review comment is based on a false premise and should be disregarded.

Git diff for build.gradle is empty—no changes are being made to these lines in this PR. The code already uses double-quoted strings with correct escape sequences (\\(, \\), \\s* in Groovy double-quoted strings correctly produce \(, \), \s* for the regex engine). There is no quote conversion happening that requires verification.

Likely an incorrect or invalid review comment.

---

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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2ac5e76 and 21fbd35.

📒 Files selected for processing (2)

• build.gradle (6 hunks)
• gradle/mavencentral.gradle (4 hunks)

🔇 Additional comments (11)

build.gradle (8)

2-15: Approved: Plugin and version strings standardized to double quotes.

Quote conversions for plugin declarations are straightforward and functionally equivalent in Groovy/Gradle.

---

21-21: Approved: Repository URL standardized to double quotes.

---

26-26: Approved: Extension variable value standardized to double quotes.

---

46-47: Approved: JUnit engine configuration strings standardized to double quotes.

---

59-82: Approved: Spotless configuration strings standardized to double quotes.

Format names, target file patterns, and formatter versions are consistently converted.

---

92-101: Approved: Error Prone compiler arguments and options standardized to double quotes.

---

105-140: Approved: Checker Framework plugin ID, checker class names, and Javac arguments standardized to double quotes.

Quote conversions maintain functional equivalence; Groovy/Gradle treat both quote styles identically for regular strings.

---

157-215: Approved: Javadoc task strings, requireJavadoc task configuration, and JVM export arguments standardized to double quotes.

Task descriptions, option strings, and JVM module export arguments are consistently converted.

gradle/mavencentral.gradle (3)

20-26: Approved: Plugin IDs, group, version, and packageName standardized to double quotes.

---

29-29: Approved: Snapshot version detection string standardized to double quotes.

---

46-82: Approved: POM metadata, license information, developer details, repository URLs, and credentials keys standardized to double quotes.

Quote conversions maintain functional equivalence. Property access methods (.get(), .getOrDefault()) remain unchanged.