Guess it is only useful if it is done in store() methods and not a new one if we want to leverage it before >=8 years (2 more lts + a few) since API cant change for j8. Means the jvm could get a system property to disable the comments and sort the keys and a new toggle on the properties object to do the same programmatically per instance.
That said Im pretty confident it will not help maven. Only useful thing is the escaping of props and it should be trivial to extract and reuse in a collector on j8 instead of using mjar or reflections which both have more cons and need the previous option anyway. Le mer. 25 août 2021 à 08:47, Michael Osipov <[email protected]> a écrit : > Am 2021-08-24 um 16:24 schrieb Robert Scholte: > > FYI: A discussion has started on core-libs-dev mailinglist[1] about > > extending java.util.Properties with methods to store properties files > > in a reproducible way. > > If you have any comments, subscribe to the mailinglist[2] or ask me to > > drop the comments. > > * Date comment must go forever > * Using Optional is purely overengineered, null is more than sufficient > * Shouldn't it be "List<String> comments" for multiline comments? > * A comparator is a nice to have, but not a must. If it is trivial to > implement, why not? > > Finally, unless this is going to land in 11 or 8 as a backport, we won't > be able to use it in the next 5 years or so... > > M > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
