neqsim-java8-rules

Validate NeqSim Java sources against Java 8 compatibility rules.

138|60|Updated Dec 5, 2018
One-click install
npx skills add https://github.com/equinor/neqsim --skill neqsim-java8-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neqsim-java8-rules
Source: https://github.com/equinor/neqsim/tree/main/.github/skills/neqsim-java8-rules
Command: npx skills add https://github.com/equinor/neqsim --skill neqsim-java8-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

All NeqSim Java code — including test classes in src/test/java — MUST compile with Java 8. The CI build will FAIL if you use Java 9+ features.

Core Features & Use Cases

  • Enforces Java 8 compatibility by forbidding Java 9+ features across the codebase.
  • Provides a clear list of forbidden features, recommended replacements, and API verification practices.
  • Ensures thorough JavaDoc requirements and consistent coding standards across NeqSim projects.

Quick Start

Run the Java 8 compatibility checks across all modules to identify and replace any Java 9+ constructs.

Frequently Asked Questions about neqsim-java8-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Java 8 compatibility in NeqSim to prevent CI build failures?

You enforce Java 8 compatibility by validating all NeqSim Java sources against Java 8 rules, explicitly checking for forbidden Java 9+ features and APIs. This prevents CI build failures across the core library and test scopes.

What Java 9+ features are forbidden when writing NeqSim Java code?

Forbidden features are any Java 9+ constructs that prevent compilation under Java 8. The compatibility rules provide a list of these forbidden features alongside recommended Java 8 replacements and required API verification practices.

Does Java 8 compatibility checking apply to NeqSim test classes?

Yes, Java 8 compatibility checking applies to all development scopes, including test classes in src/test/java. All NeqSim Java code must compile with Java 8 to avoid CI build failures.

What's the best way to scan a NeqSim codebase for Java 9+ API usage?

The best way to scan for Java 9+ API usage is to run Java 8 compatibility checks across all modules. This static analysis identifies forbidden constructs and verifies APIs against Java 8 standards.

Why does the NeqSim CI build fail when using Java 9+ features?

The NeqSim CI build fails because all Java code must compile with Java 8. Using Java 9+ features violates coding standards and triggers static analysis checks that explicitly block the build.

Are JavaDoc requirements enforced during Java 8 compatibility checks for NeqSim?

Yes, thorough JavaDoc requirements are enforced alongside Java 8 compatibility checks. The rules ensure consistent coding standards across NeqSim projects while verifying APIs and forbidding Java 9+ constructs.