On 25/08/21 5:33 pm, Magnus Ihse Bursie wrote:
...
The problem is with the time stamp, which the spec states should be
present. I understand why changing this might need a new method. But I
think we should try to steer users to this new method. Otherwise it is
likely not to be used by those who should use it (the programmers) to
the detrimental effect of users who get properties file which change
for no good reason. Having an "attractive" name is definitely part of
that. The name should scream "use me as a first hand choice for
storing properties to a file". I don't really get that feeling from
storeCanonical().
I'm not saying we should do this, but one other way to scream, is to
deprecate (but not for removal) the old "store" APIs and point the users
to the new ones (if we introduce them). Similar to what "save" API in
that same class currently does.
-Jaikiran
