The specific compiler produces deprecation warnings in both client code and the specific generated classes themselves. The field visibility should be configurable by the user.
I propose that the SpecificCompiler for the default template allow for a fieldVisibility option that is one of the below:
- 'public' fields are public, and not deprecated, this is the 1.5.x behavior
- 'public-deprecated' fields are public, and marked @Deprecated. This is the default behavior in 1.6.x
- 'private' fields are private. This may be the default in the future.