Removing need for enum attributes to be defined as keys in resource files #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a localization enum contains properties (which would be required if each enum constant required a message code for example) e.g.
and a resource bundle such as colors_en.properties
then when trying to compile with mvn clean install, the following error occurs during compilation:
colorCode is mistakenly required in the resource bundle files (e.g. colors_en.properties). The ugly workaround is to add a line in each of the resource bundle files such as
It would be much better if this ugly workaround was not required. This PR addresses the issue by only requiring ElementKind.ENUM_CONSTANT types from an enum to be present in resource bundles.
Sample Main to exercise the above classes and resources:
Sample pom.xml to compile all of the above code