• Update Gradle to nightly build 9.4.1-20260319034812
• Reorganize FAQ documentation with improved Gradle troubleshooting section
• Add comprehensive Gradle command-line execution guide
• Restructure compilation-related FAQs for better organization

Update Gradle wrapper to nightly build

• Update distributionUrl from custom JabRef build to official Gradle nightly snapshot
• Change validateDistributionUrl from false to true for security validation
• Point to gradle-9.4.1-20260319034812+0000-bin.zip from services.gradle.org

gradle/wrapper/gradle-wrapper.properties

Update Gradle wrapper script template reference

• Update template reference URL to specific Gradle commit hash
• Maintain script functionality with updated source attribution

gradlew

Reorganize FAQ with enhanced Gradle documentation

• Move Gradle section to beginning of FAQ for better visibility
• Expand Gradle troubleshooting with detailed error resolution steps
• Add comprehensive guide for running Gradle from command line using gg.cmd
• Reorganize compilation-related FAQs under new "Compilation" section header
• Remove outdated "Sync fork with upstream" GitHub workflow section

docs/code-howtos/faq.md

Description

New documentation text contains grammar and capitalization issues (e.g., Gradle builds files,
gradle run, and development versions of gradle). This violates the requirement that user-facing
text be professional and free of typos/grammar errors.

Code

docs/code-howtos/faq.md[R20-35]

+Sometimes, one needs to double-check that there is an IDE setup issue - and not an issue with modified Gradle builds files.
+It is easily possible to run Gradle from the command line without installing a separate JDK manually.
+
+1. Download [gg.cmd](https://github.com/eirikb/gg/releases/latest/download/gg.cmd). [`gg.cmd`](https://github.com/eirikb/gg) is an easy-to-use toolchain downloading all requirements.
+2. Run `gradle`:
+
+   * Linux/macOS: `sh -x ./gg.cmd gradle :jabgui:run`
+   * Windows: `.\gg.cmd gradle :jabgui:run`
+
+---
+
+Alternatively, you can install a JDK 17 (or later) and execute `./gradlew :jabgui:run`.
-To ease development, a GitHub workflow automatically updates your `main` branch daily.
-However, it is not allowed to update your files if the GitHub workflows are updated by the JabRef team.
-Therefore, GitHub notifies you now and then that "Sync fork with upstream failed for main branch".
+### Many errors during gradle run - e.g., `Unresolved reference 'jvmDependencyConflicts'.`
-To solve this issue, open your GitHub repository in your browser.
-Then, click "Sync fork" to get your fork up-to-date and get the workflow passing again.
+Gradle updates are not easy at development versions of gradle.

Evidence

PR Compliance ID 35 requires user-facing text (documentation) to be professional and free of
typos/grammar errors. The added/modified FAQ Gradle section includes multiple wording/capitalization
problems in the referenced lines.

docs/code-howtos/faq.md[20-35]
Best Practice: Learned patterns

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The newly added Gradle FAQ text has grammar/capitalization issues (e.g., `Gradle builds files`, `gradle run`, and `development versions of gradle`), which makes the documentation look unpolished.
## Issue Context
This is user-facing documentation and must be professional and free of typos/grammar errors.
## Fix Focus Areas
- docs/code-howtos/faq.md[20-35]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

In docs/code-howtos/faq.md, the new "Compilation" heading has no content because the next heading is
also level-2, so the intended subsection is not nested and the section hierarchy/TOC becomes
misleading. This appears to be an oversight introduced when adding the new parent "Compilation"
section around the existing entry.

Code

docs/code-howtos/faq.md[R193-197]

+## Compilation
-A: You have to ignore `buildSrc/src/main` as source directory in IntelliJ as indicated in our [setup guide](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace).
+## `java: package org.jabref.logic.journals does not exist`
+
+You have to ignore `buildSrc/src/main` as source directory in IntelliJ as indicated in our [setup guide](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace).

Evidence

The file consistently uses ## for major sections and ### for subsections (e.g., `## Failing
tests followed by ### Failing Checkstyle tests). In the new structure, ## Compilation` is
immediately followed by another ## ... heading, leaving the Compilation section empty and
preventing the java: package ... does not exist entry from being a nested subsection.

docs/code-howtos/faq.md[43-47]
docs/code-howtos/faq.md[193-199]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`## Compilation` is immediately followed by another `##` heading, which makes the `Compilation` section empty and breaks the document hierarchy.
### Issue Context
This section appears to be a new parent grouping for an existing FAQ entry; the child heading should be nested.
### Fix Focus Areas
- docs/code-howtos/faq.md[193-199]
### Suggested change
Change `## \`java: package org.jabref.logic.journals does not exist\`` to `### ...` (and optionally add a short intro line under `## Compilation`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools