-
Notifications
You must be signed in to change notification settings - Fork 181
Handle Java Reserved Words/Keywords #234
Comments
Maybe we can reserve some special character for these cases? |
what I did was replace all occurrences of
This is using |
Thanks for sharing this.
please do! it would be very useful. |
@jstoiko looks like I won't be able to sign the MuleSoft Contributor Agreement Acceptance [API Notebook] because of the permissions it asks for on my github account -- sorry about that. I won't be able to create a PR after all, but please feel free to use the above as a baseline, if it helps at all. |
@adjokic can you let me know what the problem is with the signing process? |
It asks to access my organizations in Github |
that's very common, to be honest. not something you should be afraid about. but of course, it is absolutely your decision and either way is fine ;) |
Variable names are now protected from being java keywords: I add "Property" to java keywords (classProperty) for example. I dropped the "_" to stay compliant to the java naming conventions and help people using sonar. I also want to do a plugin to allow for a general strategy. PS: having trouble committing. Should be solved soon. PPS: Thanks @adjokic : hadn't seen the SourceVersion stuff. :-) |
thanks @jpbelang |
thanks @adjokic you can leave this open for now |
Hi,
I am trying to find a way to deal with Java reserved words in the raml -> jax-rs generation.
This happens when I have a raml data type with, for example:
this will fail with the following error during raml generation:
[ERROR] Failed to execute goal org.raml:raml-to-jaxrs-maven-plugin:2.0.0-RC2-SNAPSHOT:generate (default-cli) on project raml: Error generating Java classes from: null: not a valid name: class -> [Help 1]
Any ideas how to deal with this the best way? A couple of things:
Thanks
The text was updated successfully, but these errors were encountered: