Add sequential run for JBang tasks

[koppor]

User description

Refs jbangdev/jbang-gradle-plugin#21 (comment)

Steps to test

See build passing on Windows, too.

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

• Enforce sequential execution of JBang tasks to prevent parallelization issues

• Add mustRunAfter dependencies between citation style and LTWA generation tasks

• Include explanatory comments about JBang gradle plugin parallelization limitations

---

Diagram Walkthrough

flowchart LR
  A["generateJournalListMV"] -- "mustRunAfter" --> B["generateCitationStyleCatalog"]
  B -- "mustRunAfter" --> C["generateLtwaListMV"]

Loading

File Walkthrough

	Relevant files
Enhancement	build.gradle.kts Add sequential execution constraints for JBang tasks          jablib/build.gradle.kts Added mustRunAfter(taskGenerateJournalListMV) to generateCitationStyleCatalog task Added mustRunAfter(taskGenerateCitationStyleCatalog) to generateLtwaListMV task Added explanatory comments about JBang gradle plugin parallelization limitations +4/-0

---

[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 ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Learned best practice	Fix typo in comment Fix the typo "parallization" to "parallelization" in the comment to maintain professional code quality and clarity. jablib/build.gradle.kts [269] -// The JBang gradle plugin doesn't handle parallization well - thus we enforce sequential execution +// The JBang gradle plugin doesn't handle parallelization well - thus we enforce sequential execution Apply / Chat Suggestion importance[1-10]: 6 __ Why: Relevant best practice - Correct typographical errors in code comments to maintain code quality and professionalism	Low
More