The vertx-codegen-api declares its own module descriptor as a module-info.java file.
The vertx-codegen-processor and vertx-codegen-json modules instead rely on moditect to generate module descriptor for the sake of preserving the execution of codegen processor tests in IDE. The codegen processor is not intended to be modular, however vertx-codegen-api and vertx-codegen-json are actually consumed by from java modules (e.g io.vertx.core module).
The absence of an module-info descriptor instructs the IDE to run tests in classpath mode which is what we need, hence the moditect is a good fit.
The vertx-codegen-api declares its own module descriptor as a
module-info.javafile.The vertx-codegen-processor and vertx-codegen-json modules instead rely on moditect to generate module descriptor for the sake of preserving the execution of codegen processor tests in IDE. The codegen processor is not intended to be modular, however vertx-codegen-api and vertx-codegen-json are actually consumed by from java modules (e.g
io.vertx.coremodule).The absence of an module-info descriptor instructs the IDE to run tests in classpath mode which is what we need, hence the moditect is a good fit.