fix Java language level in IDEA

[asolntsev]

User description

It was written as "17", though Selenium still has to support Java11+.

🔄 Types of changes

• Cleanup (formatting, renaming)

---

PR Type

Bug fix

---

Description

• Corrects Java language level from 17 to 11

• Aligns with Selenium's Java 11+ support requirement

• Updates IntelliJ IDEA project configuration files

---

Diagram Walkthrough

flowchart LR
  A["Java Language Level: 17"] -- "Downgrade to match support" --> B["Java Language Level: 11"]
  C["ij-win.bazelproject"] -- "Updated" --> B
  D["ij.bazelproject"] -- "Updated" --> B

Loading

File Walkthrough

Relevant files

Bug fix

ij-win.bazelproject Update Java language level to 11                                                  scripts/ij-win.bazelproject Changed java_language_level from 17 to 11 Aligns IntelliJ IDEA configuration with Selenium's minimum Java version requirement +1/-1      ij.bazelproject Update Java language level to 11                                                  scripts/ij.bazelproject Changed java_language_level from 17 to 11 Corrects configuration to reflect Java 11+ support requirement Includes comment about enforcing language level via .bazelrc +1/-1

---

[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: 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: Not Applicable Scope: The PR only modifies IDE configuration values (java_language_level) and introduces no runtime code paths where audit trails would apply, so compliance cannot be assessed from the diff. Referred Code java_language_level: 11 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: Configuration Naming: The changes only set the configuration key java_language_level to 11 and do not introduce code identifiers, so naming compliance cannot be fully evaluated from the diff. Referred Code java_language_level: 11 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: No Error Paths: The diff only changes IDE configuration and adds no executable logic, so error handling and edge cases cannot be assessed from the new lines. Referred Code java_language_level: 11 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: No User Errors: No user-facing error messages are introduced; as only configuration lines were modified, secure error handling cannot be evaluated from the diff. Referred Code java_language_level: 11 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: No Input Handling: The changes affect only IDE configuration and add no input handling or data processing logic, so validation and security controls cannot be assessed from the diff. Referred Code java_language_level: 11 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 ✨

No code suggestions found for the PR.