This plugin was based on kongchen's swagger-maven-plugin
This enables your Swagger-annotated project to generate Swagger specs and customizable, templated static documents during the gradle build phase. Unlike swagger-core, swagger-gradle-plugin does not actively serve the spec with the rest of the application; it generates the spec as a build artifact to be used in downstream Swagger tooling.
- Supports Swagger Spec 2.0
- Supports SpringMvc & JAX-RS
- Use Handlebars as template to customize the static document.
Import the plugin in your project by adding following configuration:
Gradle version >= 2.1
plugins {
id 'com.benjaminsproule.swagger' version '1.0.0'
}
Gradle versions < 2.1
buildscript {
repositories {
maven {
url 'https://plugins.gradle.org/m2/'
}
}
dependencies {
classpath 'gradle.plugin.com.benjaminsproule:swagger-gradle-plugin:1.0.0'
}
}
apply plugin: 'com.benjaminsproule.swagger'
swagger {
apiSource {
...
}
}
One apiSource
can be considered as a version of APIs of your service.
You can specify several apiSource
s. Generally, one is enough.
name | description |
---|---|
skipSwaggerGeneration |
If true , swagger generation will be skipped. Default is false . User property is swagger.skip |
apiSources |
List of apiSource closures. One apiSource can be considered as a version of APIs of your service. You can specify several apiSource closures, though generally one is enough. |
name | description |
---|---|
springmvc |
Tell the plugin your project is a JAX-RS(false ) or a SpringMvc(true ) project |
locations required |
Classes containing Swagger's annotation @Api , or packages containing those classes can be configured here, using ; as the delimiter. |
schemes |
The transfer protocol of the API. Values MUST be from the list: "http" , "https" , "ws" , "wss" . |
host |
The host (name or ip) serving the API. This MUST be the host only and does not include the scheme nor sub-paths. It MAY include a port. The host does not support path templating. |
basePath |
The base path on which the API is served, which is relative to the host. The value MUST start with a leading slash (/). The basePath does not support path templating. |
descriptionFile |
A Path to file with description to be set to Swagger Spec 2.0's info Object |
info required |
The basic information of the api, using same definition as Swagger Spec 2.0's info Object |
securityDefinitions |
You can put your security definitions here, see more details below |
templatePath |
The path of a handlebars template file, see more details below. |
outputPath |
The path of the generated static document, not existed parent directories will be created. If you don't want to generate a static document, just don't set it. |
outputFormats |
The format types of the generated swagger spec. Valid values are json , yaml or both json,yaml . The json format is default. |
swaggerDirectory |
The directory of generated swagger.json file. If null, no swagger.json will be generated. |
swaggerFileName |
The filename of generated filename.json file. If null, swagger.json will be generated. |
swaggerApiReader |
If not null, the value should be a full name of the class implementing com.github.kongchen.swagger.docgen.reader.ClassSwaggerReader . This allows you to flexibly implement/override the reader's implementation. Default is com.github.kongchen.swagger.docgen.reader.JaxrsReader |
attachSwaggerArtifact |
If enabled, the generated swagger.json file will be attached as a gradle artifact. The swaggerDirectory 's name will be used as an artifact classifier. Default is false . |
modelSubstitute |
The model substitute file's path, see more details below |
typesToSkip |
Nodes of class names to explicitly skip during parameter processing. More details below |
apiModelPropertyAccessExclusionsList |
Allows the exclusion of specified @ApiModelProperty fields. This can be used to hide certain model properties from the swagger spec. More details below |
jsonExampleValues |
If true , all example values in @ApiModelProperty will be handled as json raw values. This is useful for creating valid examples in the generated json for all property types, including non-string ones. |
modelConverters |
List of custom implementations of io.swagger.converter.ModelConverter that should be used when generating the swagger files. |
excludePattern |
Regex of files that will be excluded from the swagger documentation. The default is .*\\.pom so it ignores all pom files. |
If you'd like to generate a template-driven static document, such as markdown or HTML documentation, you'll need to specify a handlebars template file in templatePath
.
The value for templatePath
supports 2 kinds of path:
-
Resource in classpath. You should specify a resource path with a classpath: prefix. e.g:
classpath:/markdown.hbs
classpath:/templates/hello.html
-
Local file's absolute path. e.g:
${project.rootDir}/src/main/resources/markdown.hbs
${project.rootDir}/src/main/resources/template/hello.html
There's a standalone project for the template files, fetch them and customize it for your own project.
There're 3 types of security definitions according to Swagger Spec: basic
, apiKey
and oauth2
.
You can define multi definitions here, but you should fully follow the spec.
You can define a basic
definition like this:
securityDefinition {
name = 'MyBasicAuth'
type = 'basic'
}
or define several definitions in a json file and specify the json path like this:
securityDefinition {
json = '/securityDefinition.json'
}
The file will be read by getClass().getResourceAsStream
, so please note the path you configured.
Alternatively, specify the absolute file path to the json definition file:
securityDefinition {
jsonPath = "${basedir}/securityDefinition.json"
}
The securityDefinition.json
file should also follow the spec, one sample file like this:
{
"api_key": {
"type": "apiKey",
"name": "api_key",
"in": "header"
},
"petstore_auth": {
"type": "oauth2",
"authorizationUrl": "http://swagger.io/api/oauth/dialog",
"flow": "implicit",
"scopes": {
"write:pets": "modify pets in your account",
"read:pets": "read your pets"
}
}
}
Throughout the course of working with Swagger, you may find that you need to substitute non-primitive objects for primitive objects. This is called model substituion, and it is supported by swagger-gradle-plugin. In order to configure model substitution, you'll need to create a model substitute file. This file is a simple text file containing n
lines, where each line tells swagger-gradle-plugin to substitutes a model class with the supplied substitute. These two classes should be seperated by a colone (:
).
com.foo.bar.PetName : java.lang.String
The above model substitution configuration would tell the plugin to substitute com.foo.bar.PetName
with java.lang.String
. As a result, the generated swagger.json
would look like this ...
"definitions" : {
"Pet" : {
"properties" : {
...
"petName" : {
"type" : "string"
}
...
}
}
... instead of like this:
"definitions" : {
"Pet" : {
"properties" : {
...
"petName" : {
"$ref" : "#/definitions/PetName"
}
...
}
}
The model substitution file will be read by getClass().getResourceAsStream
, so please note the path you configured.
You can instruct swagger-gradle-plugin
to skip processing the parameters of certain types by adding the following to your build.gradle:
// TODO: Not fully supported yet
typesToSkip = [
'com.foobar.skipper.SkipThisClassPlease',
'com.foobar.skipper.AlsoSkipThisClassPlease'
}
If you'd like to exclude certain @ApiModelProperty
s based on their access
values, you may do so by adding the following as a child node of apiSource
in your build.gradle:
apiModelPropertyAccessExclusionsList = [
'secret-property'
]
The above setting would prevent internalThing
from appearing in the swagger spec output, given this annotated model:
...
@ApiModelProperty(name = "internalThing", access = "secret-property")
public String getInternalThing() {
return internalThing;
}
...
Note: In order to use apiModelPropertyAccessExclusionsList
, you must specify both the name
and access
fields of the property you wish to exclude.
To generate the swagger documentation, you need to run ./gradlew generateSwaggerDocumentation
.
N.B In previous versions (< 0.1.0) the task was swagger
, but this caused a conflict with another plugin, swagger-codegen
, (issue #8).
You can instruct swagger-gradle-plugin
to deploy the generated swagger.json
by adding the following to your build.gradle:
swaggerDirectory = "${project.rootDir}/swagger-ui"
attachSwaggerArtifact = true
The above setting attaches the generated file to Gradle for install/deploy purpose with swagger-ui
as classifier and json
as type
plugins {
id "com.benjaminsproule.swagger" version "1.0.0"
}
swagger {
apiSource {
springmvc = true
locations = [ 'com.wordnik.swagger.sample' ]
schemes = [ 'http', 'https' ]
host = 'www.example.com:8080'
basePath = '/api'
info {
title = 'Swagger Gradle Plugin Sample'
version = 'v1'
// use markdown here because I'm using markdown for output,
// if you need to use html or other markup language, you need to use your target language
description = 'This is a sample.'
termsOfService = 'http://www.example.com/termsOfService'
contact {
email = '[email protected]'
name = 'Name'
url = 'http://www.example.com'
}
license {
url = 'http://www.apache.org/licenses/LICENSE-2.0.html'
name = 'Apache 2.0'
}
}
securityDefinition {
name = 'basicAuth'
type = 'basic'
}
securityDefinition {
json = '/securityDefinition.json'
}
/**
Support classpath or file absolute path here.
1) classpath e.g: "classpath:/markdown.hbs", "classpath:/templates/hello.html"
2) file e.g: "${project.rootDir}/src/main/resources/markdown.hbs", "${project.rootDir}/src/main/resources/template/hello.html"
**/
templatePath = "${project.rootDir}/src/test/resources/strapdown.html.hbs"
outputPath = "${project.rootDir}/generated/document.html"
swaggerDirectory = "${project.rootDir}/generated/swagger-ui"
swaggerApiReader = 'com.wordnik.swagger.jaxrs.reader.DefaultJaxrsApiReader'
modelConverters = [ 'io.swagger.validator.BeanValidator' ]
// attachSwaggerArtifact = true - WILL BE ADDED IN THE FUTURE
}
}
This plugin uses the gradle-release plugin, so to release the plugin.
In ~/.gradle/gradle.properties
, bintray_user
and bintray_apiKey
need to be set for publishing to Bintray and gradle.publish.key
and gradle.publish.secret
for publishing to the central Gradle repository.
./gradlew release