swagger-api / swagger-api/swagger-codegen
[Java] plugins generates unexpected AndroidManifest.xml file
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
I'm using swagger-codegen-maven-plugin 3.0.29 . Code is being generated correctly, but there's also AndroidManifest.xml in target/generated-sources/src/main which I don't need.
Could you tell me how can I get rid of that file, please?
Swagger-codegen version
3.0.29
Swagger declaration file content or url
swagger.json - source file for CodeGen plugin
Command line used for generation
mvn clean compile
Steps to reproduce
- Run the application and visit
swagger-uipage to retrieve .json documentation file. default URL. - Copy json and save it in resources folder as
swagger.json. - run
mvn clean compileon project folder to make swagger-codegen plugin generate code in target/generated-sources folder.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked pom.xml and swagger.json, then run mvn clean compile to reproduce the extra file under target/generated-sources/src/main. Trace which configured generation step produces AndroidManifest.xml and compare it with the requested Java output. Done means the generation no longer creates the unwanted file, or the supported configuration to prevent it is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100