Closed schallee closed 12 years ago
Thanks for this contribution. I'm sorry, somehow I didn't get any notification e-mails. I'll look into this very soon! Cheers Lukas
This will be integrated as Issue 4: http://code.google.com/p/joou/issues/detail?id=4
I have not tested the system property fetching. It is very difficult to test in unit tests as the property fetching and the sizing of the cache is done at class load time. It could be done with lots of class loader foo but it's likely not worth it. It's a bit questionable as to if this property needs to be set in general. Thoughts?
In a similar vein, should issues with the property fetching and parsing be logged somewhere? If someone was trying to set the property it would be nice to know why it isn't working. java.util.logging would be the only choice with the current dependencies.
I've nearly convinced myself that having this property isn't worth it...