forked from loafle/openapi-generator-original
parent
d0770d25f5
commit
06dd7c4794
@ -48,6 +48,44 @@ mvn clean compile
|
||||
- `configOptions` - a map of language-specific parameters (see below)
|
||||
- `configHelp` - dumps the configuration help for the specified library (generates no sources)
|
||||
|
||||
### 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.
|
||||
|
||||
```xml
|
||||
<plugin>
|
||||
<groupId>io.swagger</groupId>
|
||||
<artifactId>swagger-codegen-maven-plugin</artifactId>
|
||||
<version>${swagger-codegen-maven-plugin-version}</version>
|
||||
<executions>
|
||||
<execution>
|
||||
<goals>
|
||||
<goal>generate</goal>
|
||||
</goals>
|
||||
<configuration>
|
||||
<inputSpec>src/main/resources/yaml/yamlfilename.yaml</inputSpec>
|
||||
<!-- language file, like e.g. JavaJaxRSCodegen shipped with swagger -->
|
||||
<language>com.my.package.for.GeneratorLanguage</language>
|
||||
<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](examples) for using the plugin
|
Loading…
x
Reference in New Issue
Block a user