====== 5.4 Java Environment ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:05-development-environment:start | Return to Development Environment ]]

If Phase 0 uses Java for any runtime [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], the generated [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] binding, the build process, or the [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validation]] utility, the team should define the required Java environment. This includes the Java Development Kit version, expected build tool, environment variables, generated source locations, classpath or module requirements, and execution commands.

The team should distinguish Java runtime requirements from Java development requirements. A developer who only inspects documentation may not need the Java toolchain. A developer who builds Java Nodes, compiles generated bindings, or runs Java-based Validation tools will need the required JDK and supporting build tools.

The Java environment should avoid undocumented local assumptions. Build commands should run from documented [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] locations. Dependencies should be declared through the selected build mechanism rather than through manually configured local classpaths.

If the team does not use Java in Phase 0, this section should state that Java remains out of scope for the current [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]. If the team later adds Java Nodes or Java-generated DDS [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Types]], the handbook should update this section before those [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] are added to the controlled Baseline.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>