There is no particular reason to forbid use of @Messages on fields, it was just not initially thought useful. In fact sometimes it is desirable; either code traditionally kept a localized String as a field (better refactored to be inlined of course), or the field initializer is of an anonymous inner class which uses a bundle string in some method.
Created attachment 114308 [details]
Right, I need that for issue 190129 as well.
Makes sense; see the diff to the existing GroupOptionProcessor.
Integrated into 'main-golden'
User: Jesse Glick <email@example.com>
Log: #206543: permit @NbBundle.Messages on fields.