-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Media type not supported (Javadoc?) #190
Comments
Hi @dizzzz, Could you isolate the issue? do you have an example endpoint which reproduces it? |
I will try! One question I have (to understand the design a bit better): what is the purpose of reading javadoc details? I guess somewhere some rotten javadoc code is written, how robust is this part of the code? If it is left out... what is missing? |
Is there a way to see on which .java file an issue occurs? |
It is on the stacktrace |
@rmpestano :-) I meant the file that is being parsed by the tool. My question is related to my earlier question. I think we have some missing / wrong / inconsistent javadoc syntax, but can't yet figure out which one. |
Ohh my bad, I don't think so, If you can zip your project I can try to find out by debuging (probably something related to the javadoc as the error is on the javadoc parser) |
@rmpestano unfortunately I cannot send the code (completely), an 'anonymized' part would be feasible but for this I need to know which file I need to check. |
maybe the debugger can help here? |
Yes, install this project locally (mvn install) then install https://github.com/sdaschner/jaxrs-analyzer-maven-plugin and then upgrade your project to use the installed maven plugin and finally run If find any problems trying to debug just ask for help here. the error is here, if you put a breakpoint here you may find the endpoint which has the invalid javadoc tag. |
@rmpestano My question remains: how is the contents of the javadoc used in the end result? |
it is used to enhance the generated swagger.json, e.g add description to endpoint params, return types and so on, see an example here. |
When running the plugin I have the following trace; is there any way to work around this?
The text was updated successfully, but these errors were encountered: