jeo:assemble

Full name:

org.eolang:jeo-maven-plugin:0.11.4:assemble

Description:

Assembles XMIR representation of Java bytecode into executable class files.

This Maven plugin converts low-level EO representation (in XMIR format) into Java bytecode that can be executed by the Java Virtual Machine. The plugin performs pure assembly without applying any optimizations or improvements to the bytecode.

The plugin supports optional bytecode verification to ensure generated classes are valid and can be loaded by the JVM.

Attributes:

Requires a Maven project to be executed.
The goal is not marked as thread-safe and thus does not support parallel builds.
Since version: 0.1.0.
Binds by default to the lifecycle phase: process-classes.

Optional Parameters

Name	Type	Since	Description
`<disabled>`	`boolean`	`0.2.0`	Flag to disable the plugin execution. When set to `true`, the plugin will skip all processing and exit immediately. This can be useful for conditional builds or troubleshooting. Default: `false` User Property: `jeo.assemble.disabled`
`<outputDir>`	`File`	`0.2.0`	Target directory for generated bytecode class files. All assembled class files will be written to this directory, preserving the package structure as defined in the source XMIR files. Default: `${project.build.outputDirectory}` User Property: `jeo.assemble.outputDir`
`<skipVerification>`	`boolean`	`0.2.0`	Flag to skip bytecode verification after assembly. By default, all generated bytecode is verified to ensure it conforms to JVM specifications and can be loaded without errors. Set this parameter to `true` to skip verification, which may speed up the build but could result in invalid class files. Default: `false` User Property: `jeo.assemble.skip.verification`
`<sourcesDir>`	`File`	`0.2.0`	Source directory containing XMIR files to be assembled. This directory should contain EO files in XMIR format that represent Java bytecode instructions. These files are typically generated by the disassemble goal. Default: `${project.build.directory}/generated-sources/jeo-xmir` User Property: `jeo.assemble.sourcesDir`
`<xmirVerification>`	`boolean`	`0.8.0`	Flag to enable XMIR verification before assembling. When enabled, verifies all XMIR files for structural integrity and correctness before attempting to assemble them into bytecode. If any XMIR file is invalid or corrupted, the build process will fail. This verification is disabled by default for performance. Default: `false` User Property: `jeo.assemble.xmir.verification`

Parameter Details

<disabled>

Flag to disable the plugin execution.

When set to true, the plugin will skip all processing and exit immediately. This can be useful for conditional builds or troubleshooting.

Type: boolean
Since: 0.2.0
Required: No
User Property: jeo.assemble.disabled
Default: false

<outputDir>

Target directory for generated bytecode class files.

All assembled class files will be written to this directory, preserving the package structure as defined in the source XMIR files.

Type: java.io.File
Since: 0.2.0
Required: No
User Property: jeo.assemble.outputDir
Default: ${project.build.outputDirectory}

<skipVerification>

Flag to skip bytecode verification after assembly.

By default, all generated bytecode is verified to ensure it conforms to JVM specifications and can be loaded without errors. Set this parameter to true to skip verification, which may speed up the build but could result in invalid class files.

Type: boolean
Since: 0.2.0
Required: No
User Property: jeo.assemble.skip.verification
Default: false

<sourcesDir>

Source directory containing XMIR files to be assembled.

This directory should contain EO files in XMIR format that represent Java bytecode instructions. These files are typically generated by the disassemble goal.

Type: java.io.File
Since: 0.2.0
Required: No
User Property: jeo.assemble.sourcesDir
Default: ${project.build.directory}/generated-sources/jeo-xmir

<xmirVerification>

Flag to enable XMIR verification before assembling.

When enabled, verifies all XMIR files for structural integrity and correctness before attempting to assemble them into bytecode. If any XMIR file is invalid or corrupted, the build process will fail. This verification is disabled by default for performance.

Type: boolean
Since: 0.8.0
Required: No
User Property: jeo.assemble.xmir.verification
Default: false