You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by Daniel Jemiolo <da...@us.ibm.com> on 2006/08/02 04:38:22 UTC
MUSE-33 proposal
I have completed part of MUSE-33, the only open item for M2, and have a
suggestion for the rest of it that I would like to run by the team:
The last part of MUSE-33 requires me to make sure that all error messages
are in the right .properties files, that there are no duplicates, etc.
This is a very tedious process, as there are about 400 Java and properties
files in the source tree. Yesterday I designed a program that could
traverse the tree and
1. move error message entries that were in the wrong properties file to
the right file,
2. remove unused error messages, and
3. remove duplicate error messages
I believe that I could implement, test, and verify the results of this
program in 1-2 days. The results would not be 100% perfect (it could not
account for things like one-off misspellings of message names), but they
would be much more accurate (percentage-wise) than if I went through 400
files manually over the course of a week. We would then be in a position
to fix the occasional misspelled message key, which is much better than
the current situation.
The issue I have is that I do not have the 1-2 days to write/verify this
program before M2. I am comfortable moving this to the 2.0 release since I
have a solution designed and it will provide much better results than
spending a week on manual fixes. If no one has any objections, I will
change the due date on MUSE-33 to 8/17/06 during our Thursday status call.
Dan
Dan Jemiolo
IBM Corporation
Research Triangle Park, NC
+++ I'm an engineer. I make slides that people can't read. Sometimes I eat
donuts. +++
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org