Re-enable JavaDoc formatting

[koppor]

User description

I saw

Reason:

howto says: enable JavaDoc formatting:

Thus, we have an inconsistency.

Let's try how JavaDoc formattig works? ^^

Upstream issues

• IntelliJ issue of the Markdown case: https://youtrack.jetbrains.com/issue/IDEA-381474/Unexpected-extra-spaces-after-formatting-Javadocs-with-using-comment-style
• JBang shebang formatting issue: https://youtrack.jetbrains.com/issue/IDEA-384956/Skip-formatting-of-shebang-headers

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Enhancement

---

Description

• Re-enable JavaDoc formatting in project code style settings

• Removes explicit disable flag to use default formatting behavior

• Aligns project configuration with documentation guidelines

---

Diagram Walkthrough

flowchart LR
  A["Project Code Style Config"] -- "Remove ENABLE_JAVADOC_FORMATTING=false" --> B["JavaDoc Formatting Enabled"]

Loading

File Walkthrough

	Relevant files
Configuration changes	Project.xml Remove JavaDoc formatting disable flag                                      .idea/codeStyles/Project.xml Removed ENABLE_JAVADOC_FORMATTING option set to false Allows JavaDoc formatting to use default behavior Resolves inconsistency between project settings and documentation +0/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

No code suggestions found for the PR.

[koppor]

Not a good idea it seems