I think that is a fantastically good/important idea.
E.g. the more unlikely/unusual the error, the more critical the error
message is and the more unlikely that it will ever get tested.
Jerome Dochez wrote:
> Bill Shannon wrote:
>> Jerome Dochez wrote:
>>> if you are an owner, you are responsible for moving the
>>> LogStrings.properties file (while cleaning obsolete content) or
>>> finding a new owner for that file if it is not one of yours.
>>
>> Could a FindBugs detector find missing or unused properties
>> for logging strings? Do we have anyone who knows how to write
>> a FindBugs detector?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
> most of the tools that I know of are finding keys in code which don't
> have associated entries in the module's LogStrings.properties but I
> have never heard of a tool to reconcile classes and properties files.
> I don't think we have anyone with FindBugs experience.
>
> Jerome
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
--
Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell 650-784-4123 - Sun Microsystems, Inc.