- to simplify the properties load, I'd have to refactor this block of code out of there (because it could be useful on other places, too, and we don't have nothing on this) ... in core (org.apache.pivot.util) we have Resources, so what do you think on add something (very simple) in this package ? -- Given the name of the resource, it uses a PropertiesSerializer, load it, and return a Map<String, String> hiding all details.
This sounds like a pretty trivial convenience class. In general, we try to stay away from classes like this (since it is already easy enough to do what you describe using PropertiesSerializer itself). Also, as you pointed out, Pivot tends to emphasize the use of JSON over properties files, so the existence of such a class would be inconsistent.
-- Later another little enahncements could be the ability to set the Locale, to change a little its behavior, like in resource.
I'm not sure how a Locale would apply here. As far as I know, normal properties files (as opposed to resource bundle properties files) are locale-independent.
G
