Add options that allow separating the generation of non-schema code and schema code (serialization classes):
--schemaprojectname {name} specifies a separate project name (package name, namespace name, etc.) for the emitted schema classes. If set, the schema classes are emitted into a separate project and referenced from the code project.
--nocode skips emitting all non-schema code (consumers, producers, etc.) but does run through the code templates to collect the required schema references.
-- noschemas skips emitting schema code.
The combination --schemaprojectname and --noschema emits code that references an external project containing the schemas that was generated separately.
The combination --schemaprojectname {name} and --nocode emits a schema-only project.
Just specifying --schemaprojectname {name} emits two projects with the code project referencing the schema project.
Add options that allow separating the generation of non-schema code and schema code (serialization classes):
--schemaprojectname {name}specifies a separate project name (package name, namespace name, etc.) for the emitted schema classes. If set, the schema classes are emitted into a separate project and referenced from the code project.--nocodeskips emitting all non-schema code (consumers, producers, etc.) but does run through the code templates to collect the required schema references.-- noschemasskips emitting schema code.The combination
--schemaprojectnameand--noschemaemits code that references an external project containing the schemas that was generated separately.The combination
--schemaprojectname {name}and--nocodeemits a schema-only project.Just specifying
--schemaprojectname {name}emits two projects with the code project referencing the schema project.