Add Gradle support and keep Ant support

[jwaisner]

PR Type

Enhancement, Documentation

---

Description

• Add comprehensive Gradle 9.2.0 build system support

• Maintain full backward compatibility with Apache Ant

• Create detailed documentation for Gradle setup and usage

• Configure Gradle properties for optimal build performance

---

Diagram Walkthrough

flowchart LR
  A["Gradle 9.2.0<br/>C:\Gradle\bin"] -->|"Build System"| B["build.gradle<br/>settings.gradle"]
  B -->|"Configuration"| C["gradle.properties<br/>JVM & Cache Settings"]
  C -->|"Execution"| D["Gradle Tasks<br/>with Ant Prefix"]
  D -->|"Backward Compatible"| E["Apache Ant<br/>All Tasks Work"]
  F["Documentation"] -->|"Setup Guide"| G["HOW_TO_USE_GRADLE.md"]
  F -->|"Overview"| H["README_GRADLE.md"]

Loading

File Walkthrough

	Relevant files
Documentation	HOW_TO_USE_GRADLE.md Complete Gradle setup and troubleshooting guide                    HOW_TO_USE_GRADLE.md Comprehensive guide for Gradle setup and configuration Documents two options: using full path or adding to PATH Includes PowerShell script setup, manual PATH configuration, and alias creation Provides troubleshooting section for common issues and verification steps +209/-0  README_GRADLE.md Gradle build system overview and quick reference                  README_GRADLE.md Overview of Gradle 9.2.0 integration with Bearsampp Development Kit Quick start guide with basic commands for build setup and execution Documents Ant compatibility with ant- prefix for all existing tasks Lists key features including performance improvements and modern tooling benefits +187/-0
Configuration changes	gradle.properties Gradle build configuration and performance settings            gradle.properties Configure JVM arguments for Gradle daemon with 2GB heap and memory dump on OOM Enable Gradle daemon, parallel execution, and build cache for performance Set console output to auto and file encoding to UTF-8 Define project-specific properties for version and group identification +26/-0

---

[qodo-code-review]

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: 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: 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: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit logs: The added documentation and Gradle properties introduce new build commands and integrations without indicating any audit logging of critical actions, but as this PR primarily adds docs/config, logging may be handled elsewhere. Referred Code ### Basic Commands ```powershell # Information gradle tasks # List all available tasks gradle info # Show build configuration gradle verify # Verify build environment gradle --version # Show Gradle version # Build Setup gradle initDirs # Initialize build directories gradle loadLibs # Download required libraries gradle loadAntLibs # Load libraries using Ant # Build & Clean gradle clean # Clean build artifacts gradle build # Build project gradle hashAll # Generate hash files </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td><details> <summary><strong>Generic: Robust Error Handling and Edge Case Management</strong></summary><br> **Objective:** Ensure comprehensive error handling that provides meaningful context and graceful <br>degradation<br> **Status:** <br><a href='https://github.com/Bearsampp/dev/pull/37/files#diff-bfb11dfbe38e451307a385c1b89654a19e41e05bd5677d74a34760e37c8f22b8R131-R161'><strong>Error handling docs</strong></a>: The PR adds usage and troubleshooting guidance but no executable code paths or handlers; <br>robust error handling for any new tasks or scripts referenced may exist elsewhere and <br>cannot be verified from this diff.<br> <details open><summary>Referred Code</summary> ```markdown ## Troubleshooting ### "gradle is not recognized" **Problem:** Gradle not in PATH **Solutions:** 1. Use full path: `C:\Gradle\bin\gradle tasks` 2. Add to PATH (see above) 3. Create alias (see above) ### "Cannot find path" **Problem:** Wrong directory **Solution:** ```powershell cd D:\Bearsampp-dev\dev C:\Gradle\bin\gradle tasks ... (clipped 10 lines) </details> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td><details> <summary><strong>Generic: Security-First Input Validation and Data Handling</strong></summary><br> **Objective:** Ensure all data inputs are validated, sanitized, and handled securely to prevent <br>vulnerabilities<br> **Status:** <br><a href='https://github.com/Bearsampp/dev/pull/37/files#diff-3d103fc7c312a3e136f88e81cef592424b8af2464c468116545c4d22d6edcf19R1-R26'><strong>Security context</strong></a>: The new Gradle properties and documentation do not introduce input handling code, so <br>validation and secure data handling for build tasks cannot be assessed from this diff and <br>may be defined elsewhere.<br> <details open><summary>Referred Code</summary> ```ini # Gradle Build Properties for Bearsampp Development Kit # JVM settings for Gradle daemon org.gradle.jvmargs=-Xmx2048m -XX:MaxMetaspaceSize=512m -XX:+HeapDumpOnOutOfMemoryError # Enable Gradle daemon for faster builds org.gradle.daemon=true # Enable parallel execution org.gradle.parallel=true # Enable build cache org.gradle.caching=true # Configure console output org.gradle.console=auto # Enable configuration on demand (faster for multi-project builds) org.gradle.configureondemand=false # File encoding ... (clipped 5 lines) 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-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Adopt the Gradle Wrapper for portability The current build process depends on a hardcoded local Gradle installation (C:\Gradle\bin), making it non-portable. It is suggested to adopt the standard Gradle Wrapper (gradlew) to ensure reproducible builds across different environments without manual setup. Examples: HOW_TO_USE_GRADLE.md [5-18] Gradle is installed at `C:\Gradle\bin` but is **NOT in your PATH**. ## Two Options ### Option 1: Use Full Path (Works Now) Use the full path to gradle.bat: ```powershell C:\Gradle\bin\gradle tasks ... (clipped 4 lines) README_GRADLE.md [5-13] The Bearsampp Development Kit now uses **Gradle 9.2.0** from your local installation at `C:\Gradle\bin` with full backward compatibility with Apache Ant. ## Quick Start ### Prerequisites - ✓ Gradle 9.2.0 installed at `C:\Gradle\bin` - ✓ Java 11+ (you have Java 23.0.2) - ✓ Gradle added to System PATH Solution Walkthrough: Before: // In documentation files like HOW_TO_USE_GRADLE.md # Current Situation Gradle is installed at `C:\Gradle\bin` but is NOT in your PATH. # Option 1: Use Full Path C:\Gradle\bin\gradle tasks C:\Gradle\bin\gradle info # Option 2: Add to PATH (Permanent Solution) 1. Run PowerShell as Administrator 2. Run the setup script `.\add-gradle-to-path.ps1` 3. Restart PowerShell After: // In a simplified README.md # How to build The project uses the Gradle Wrapper, which requires no manual installation. # Prerequisites - Java 11+ # Build the project # On Windows: ./gradlew.bat build # On Linux/macOS: ./gradlew build Suggestion importance[1-10]: 10 __ Why: The suggestion correctly identifies a critical design flaw—relying on a hardcoded local Gradle installation—and proposes the industry-standard Gradle Wrapper, which is essential for build portability and reproducibility.	High
General	Correct a misleading performance setting Set org.gradle.configureondemand to true and update its comment to correctly reflect that this setting improves performance for multi-project builds. gradle.properties [18-19] -# Enable configuration on demand (faster for multi-project builds) -org.gradle.configureondemand=false +# Enable configuration on demand for potentially faster multi-project builds. +# Gradle will only configure projects relevant to the requested tasks. +org.gradle.configureondemand=true [Suggestion processed] Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a misleading comment and a suboptimal performance setting, proposing a change that aligns with Gradle's documentation and improves build performance.	Medium
	Avoid hardcoding paths in documentation Replace hardcoded absolute paths in the documentation with placeholders or environment variables to make the instructions more portable and universally applicable. HOW_TO_USE_GRADLE.md [5-24] -Gradle is installed at `C:\Gradle\bin` but is **NOT in your PATH**. +This guide assumes Gradle is installed in a known location (e.g., `C:\Gradle`) and the project is at `D:\Bearsampp-dev\dev`. Please adjust the paths in the examples to match your local setup. For a more portable setup, consider using environment variables like `%GRADLE_HOME%` and `%PROJECT_HOME%`. + ... -Use the full path to gradle.bat: + +Use the full path to your gradle executable. For example, if Gradle is in `C:\Gradle\bin`: ```powershell C:\Gradle\bin\gradle tasks C:\Gradle\bin\gradle info C:\Gradle\bin\gradle verify C:\Gradle\bin\gradle release Example: -cd D:\Bearsampp-dev\dev +# Navigate to your project directory first +cd path\to\your\project +# Then run the Gradle command C:\Gradle\bin\gradle info `[To ensure code accuracy, apply this suggestion manually]` <details><summary>Suggestion importance[1-10]: 6</summary> __ Why: The suggestion correctly points out that hardcoded paths in the documentation harm portability and usability, and the proposed change makes the guide more generic and helpful for other developers. </details></details></td><td align=center>Low </td></tr> <tr><td align="center" colspan="2"> - [ ] More <!-- /improve --more_suggestions=true --> </td><td></td></tr></tbody></table>

[qodo-code-review]

Suggestion: Correct a misleading performance setting

Suggested change

	# Enable configuration on demand (faster for multi-project builds)
	org.gradle.configureondemand=false
	# Enable configuration on demand for potentially faster multi-project builds.
	# Gradle will only configure projects relevant to the requested tasks.
	org.gradle.configureondemand=true

[N6REJ]

new pr see #38