Skip to content
Branch: master
Find file History
Latest commit 54b3d6e Dec 30, 2019


swagger-gradle-plugin supports gradle 3.2 and higher.


Gradle 3.2 and higher

plugins {
  id "io.swagger.core.v3.swagger-gradle-plugin" version "2.1.1"

Gradle 1.x and 2.0

NOTE: Since version 2.0.10 gradle 1.x and 2.x up to 3.1 are not supported.

with versions up to 2.0.9:

buildscript {
  repositories {
    maven {
      url ""
  dependencies {
    classpath "io.swagger.core.v3:swagger-gradle-plugin:2.1.1"

apply plugin: "io.swagger.core.v3.swagger-gradle-plugin"



  • Resolves project openAPI specification and saves the result in JSON, YAML or both formats. All parameters except outputFileName, outputFormat, classpath, skip, encoding, outputDir and outputPath correspond to swagger configuration property with same name.

Example Usage

resolve {
    outputFileName = 'PetStoreAPI'
    outputFormat = 'JSON'
    prettyPrint = 'TRUE'
    classpath = sourceSets.main.runtimeClasspath
    resourcePackages = ['io.test']
    outputDir = file('test')


Parameter Description Required Default
classpath classpath for resources to scan (swagger and deps already included in classpath) true
outputDir output path where file(s) are saved true
outputFileName file name (no extension) false openapi
outputFormat file format (JSON, YAML, JSONANDYAML false JSON
skip if TRUE skip execution false FALSE
encoding encoding of output file(s) false
resourcePackages see configuration property false
resourceClasses see configuration property false
prettyPrint see configuration property false TRUE
openApiFile openapi file to be merged with resolved specification, equivalent to config openAPI false
filterClass see configuration property false
readerClass see configuration property false
scannerClass see configuration property false
readAllResources see configuration property false
ignoredRoutes see configuration property false
objectMapperProcessorClass see configuration property false
modelConverterClasses see configuration property false
contextId see Context false
outputPath DEPRECATED output path where file(s) are saved false

Note parameter openApiFile corresponds to config openAPI. It points to a location of a file in YAML or JSON format representing the input spec that will be merged with the resolved spec. Typically used to add Info section, or any other meta data. An example of such file:

openapi: 3.0.1
  version: '1.0'
  title: Swagger Pet Sample App Config File
  description: 'This is a sample server Petstore server.  You can find out more
    about Swagger at []( or on [,
    #swagger](  For this sample, you can use the api key
    special-key to test the authorization filters.'
    name: Apache 2.0
You can’t perform that action at this time.