forked from loafle/openapi-generator-original
* Validate spec on generation by default Adds a validation parameter to CodegenConfigurator, and passes through options from CLI, Maven Plugin and Gradle Plugin to that property. Default is to validate the spec during generation. If spec has errors, we will output errors as well as warnings to the user. Option can be disabled by passing false to validateSpec (Maven/Gradle) or --validate-spec (CLI). * Prepare version 3.1.1-SNAPSHOT * fix version * Use last prod version for the sample * Update README.md Fix * [cli] Option parser does not support true/false for boolean options
openapi-generator-maven-plugin
A Maven plugin to support the OpenAPI generator project
Usage
Add to your build->plugins section (default phase is generate-sources phase)
<plugin>
<groupId>org.openapitools</groupId>
<artifactId>openapi-generator-maven-plugin</artifactId>
<version>3.1.2</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<inputSpec>${project.basedir}/src/main/resources/api.yaml</inputSpec>
<generatorName>java</generatorName>
<configOptions>
<sourceFolder>src/gen/java/main</sourceFolder>
</configOptions>
</configuration>
</execution>
</executions>
</plugin>
Followed by:
mvn clean compile
General Configuration parameters
inputSpec- OpenAPI Spec file pathvalidateSpec- Whether or not to validate the input spec prior to generation. Invalid specifications will result in an error.language- target generation language (deprecated, replaced bygeneratorNameas values here don't represent only 'language' any longer)generatorName- target generator nameoutput- target output path (default is${project.build.directory}/generated-sources/swagger)templateDirectory- directory with mustache templatesaddCompileSourceRoot- add the output directory to the project as a source root (trueby default)modelPackage- the package to use for generated model objects/classesapiPackage- the package to use for generated api objects/classesinvokerPackage- the package to use for the generated invoker objectsmodelNamePrefixandmodelNameSuffix- Sets the pre- or suffix for model classes and enumswithXml- enable XML annotations inside the generated models and API (only works with Javalanguageand libraries that provide support for JSON and XML)configOptions- a map of language-specific parameters (see below)configHelp- dumps the configuration help for the specified library (generates no sources)ignoreFileOverride- specifies the full path to a.openapi-generator-ignoreused for pattern based overrides of generated outputsgenerateApis- generate the apis (trueby default)generateApiTests- generate the api tests (trueby default. Only available ifgenerateApisistrue)generateApiDocumentation- generate the api documentation (trueby default. Only available ifgenerateApisistrue)generateModels- generate the models (trueby default)modelsToGenerate- A comma separated list of models to generate. All models is the default.generateModelTests- generate the model tests (trueby default. Only available ifgenerateModelsistrue)generateModelDocumentation- generate the model documentation (trueby default. Only available ifgenerateModelsistrue)generateSupportingFiles- generate the supporting files (trueby default)supportingFilesToGenerate- A comma separated list of supporting files to generate. All files is the default.skip- skip code generation (falseby default. Can also be set globally through thecodegen.skipproperty)
Custom Generator
Specifying a custom generator is a bit different. It doesn't support the classpath:/ syntax, but it does support the fully qualified name of the package. You can also specify your custom templates, which also get pulled in. Notice the dependency on a project, in the plugin scope. That would be your generator/template jar.
<plugin>
<groupId>org.openapitools</groupId>
<artifactId>openapi-generator-maven-plugin</artifactId>
<version>${openapi-generator-maven-plugin-version}</version>
<executions>
<execution>
<goals>
<goal>generate</goal>
</goals>
<configuration>
<inputSpec>${project.basedir}/src/main/resources/yaml/yamlfilename.yaml</inputSpec>
<!-- language file, like e.g. JavaJaxRSCodegen -->
<generatorName>com.my.package.for.GeneratorLanguage</generatorName>
<templateDirectory>myTemplateDir</templateDirectory>
<output>${project.build.directory}/generated-sources</output>
<apiPackage>${default.package}.handler</apiPackage>
<modelPackage>${default.package}.model</modelPackage>
<invokerPackage>${default.package}.handler</invokerPackage>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.my.generator</groupId>
<artifactId>customgenerator</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
Sample configuration
Please see an example configuration for using the plugin. To run these examples, explicitly pass the file to maven. Example:
mvn -f non-java.xml compile