create or identify a tool to locate orphan messages
---------------------------------------------------
Key: MIFOS-4712
URL: http://mifosforge.jira.com/browse/MIFOS-4712
Project: mifos
Issue Type: Improvement
Components: Internationalization, Localization
Reporter: Adam Monsen
Priority: Major
Fix For: Release G - Iteration 1, Release G
Orphan messages impede translators and developers.
Create (or identify) a tool to help developers locate orphan (unused) messages.
# Identify message keys.
# Search through some combination of .ftl, .jsp, .java, .xml files for each key.
# Output a list of keys that do not appear to be used anywhere.
# Use Bash Shell/Groovy/Python/Java... something most devs have easy access to.
# Optional: support a list of excluded keys. This would be useful for keys we
know are cobbled together in code.
This tool doesn't have to be 100% perfect, it just has to be helpful. It should
assume that developers will be smart and interpret the results of the tool
rather than trust it completely.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
