[java] add missing bazel artifacts by titusfortner · Pull Request #16773

[java] add missing bazel artifacts by titusfortner · Pull Request #16773 · SeleniumHQ/selenium

Security Compliance

🟢

No security concerns identified

No security vulnerabilities detected by AI analysis. Human verification advised for critical code.

Ticket Compliance

🟡

🔴	Ensure that calling `click()` on a link with `javascript:` in its `href` triggers the JavaScript (regression in Selenium 2.48 on Firefox 42 compared to 2.47.1).
	Provide a fix (or change) so the referenced test case alerts again when clicked in the affected environment (Firefox 42, Selenium 2.48.x).

🟡

🎫 #5678

🔴	Fix or explain the repeated ChromeDriver instantiation issue that produces `Error:` `ConnectFailure (Connection refused)` on subsequent instances (Ubuntu 16.04.4, Selenium 3.9.0, Chrome 65, ChromeDriver 2.35).
	Ensure multiple ChromeDriver instances can be created without connection-refused errors in the described environment.

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