swagger-api / swagger-api/swagger-codegen
Package to scan when packing an ear
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
We have the following structure:
- blabla.ear
-> libs
-> service clases here
-> war
-> swagger conf etc.
The problem is that the services clases are loadad by a different classloader than the one that load the swagger clases.
Is there a place to configure the classloader used to find the classes?
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
The issue identifies an EAR containing a libs directory and a WAR with Swagger configuration, but names no repository files or tests. Start by locating the EAR/WAR packaging and class-loading entry points, then determine whether the package to scan or classloader can be configured; done means the services and Swagger classes are discoverable under the intended classloader.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100