[
https://jira.jboss.org/jira/browse/JBTM-263?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-263:
----------------------------------------
It would be nice if the tool also caught 'declared but not used' and 'used but
not declared' cases, as these arise due to typos or other inconsistency between
occurrences of what should be the same message key value.
improve logging robustness
--------------------------
Key: JBTM-263
URL:
https://jira.jboss.org/jira/browse/JBTM-263
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Common
Affects Versions: 4.2.3.SP5
Reporter: Jonathan Halliday
Assignee: Andrew Dinn
Priority: Minor
Fix For: future
Some @message tags are in normal comments rather than javadoc comments, so they don't
get processed into message bundles. Some are missing entirely. It should be possible to
develop tooling to detect these at build time by checking against log statements in the
code. Also, make the logging more robust in the case where errors are missing - a generic
message should be printed in preference to crashing as sometimes happens now. See also
JBTM-231.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira