Hi,
I'm finding the idea of removing the hardcoded timestamp and adding a
property to restore compatibility
strangely attractive. I don't think we've yet found a case where the
timestamp was needed (but need to keep looking).
(Adding a timestamp to the comment by the caller of store() is already
possible)
It will reveal where the timestamp is needed (via some kind of failure,
though perhaps not a timely one)
and includes a fallback mechanism when needed.
It will generally cleanup up the behavior of an old API.
The other approaches make new work for developers based on unclear
requirements.
$.02, Roger
On 8/27/21 1:38 PM, Robert Scholte wrote:
I've dropped this topic on the Maven Dev mailinglist as well[1].
The responses are mixed, so I'd prefer to refer to the mailinglist
instead of summarizing the responses here.
This will prevent that those opinions are considered my opinions.
Thanks,
Robert
[1]
https://lists.apache.org/thread.html/r687bca66bb548d3a13ea665fb7202daf9710564802fa497a4b34d81e%40%3Cdev.maven.apache.org%3E
