swagger-api / swagger-api/swagger-codegen

build failure: Failure In Test suite

Open
#10,023 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

I want to build swagger-codegen to get swagger-codegen.jar. I have set JAVA_HOME and maven paths.

mvn -version
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: D:\apache-maven-3.6.3\bin..
Java version: 1.8.0_202, vendor: Eclipse OpenJ9, runtime: C:\Program Files\AdoptOpenJDK\jdk-8.0.202.08\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

java -version
openjdk version "1.8.0_202"
OpenJDK Runtime Environment (build 1.8.0_202-b08)
Eclipse OpenJ9 VM (build openj9-0.12.1, JRE 1.8.0 Windows 10 amd64-64-Bit Compressed References 20190205_265 (JIT enabled, AOT enabled)
OpenJ9 - 90dd8cb40
OMR - d2f4534b
JCL - d002501a90 based on jdk8u202-b08)

When I attempt to compile the source using

mvn -e clean package

It ends with error in test suite. I have tried using latest as well as 2.4.12 version but getting similar error.

Swagger-codegen version

2.4.12
Latest

Swagger declaration file content or url
Command line used for generation

TestSuite.txt

Steps to reproduce

mvn -e clean package

Related issues/PRs
Suggest a fix/enhancement

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached TestSuite.txt and reproduce the reported failure using mvn -e clean package on the stated Windows 10 and Java 8 environment. Compare the test-suite error with the provided Java and Maven versions; the issue is done when the cause is identified and a reproducible fix or diagnosis is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.