-
Notifications
You must be signed in to change notification settings - Fork 42
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
wisdom-raml-plugin doesn't support route url described using constants #564
Comments
So, it seems the issue can be sourced to |
@barjoWDYT ? |
Riduidel
added a commit
to Riduidel/wisdom
that referenced
this issue
Nov 16, 2016
Riduidel
added a commit
to Riduidel/wisdom
that referenced
this issue
Nov 16, 2016
… be referenced in annotation. The following are supported : - direct field access - access to field declared in an inner class or interface The following are not supported - access to field declared in another class, even if in the same package - access to a class defined from an expression (which can't happen, but is nevertheless considered as valid by javaparser)
Sorry I missed that one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use to write my routes the following way (cause I'm fan of clearly separated informations)
When doing so, wisdom-raml-maven-plugin generates the following RAML file
This is obviously incorrect.
My understanding is that this plugin performs some source code parsing in order to get the javadoc. Unfortunatly, this parsing fails to read the constant I use in annotation. I guess it may be due to wisdom-source-model which ignore references to constants in annotations.
The text was updated successfully, but these errors were encountered: