Changeset 17564 in josm for trunk/src/org/openstreetmap


Ignore:
Timestamp:
2021-03-15T13:53:05+01:00 (4 years ago)
Author:
Don-vip
Message:

fix #20594 - add robustness to AutomaticCombine when Integer values cannot be parsed

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/org/openstreetmap/josm/gui/conflict/tags/TagConflictResolutionUtil.java

    r17093 r17564  
    298298        public String resolve(Set<String> values) {
    299299            Set<String> results = instantiateSortedSet();
    300             for (String value: values) {
    301                 String[] parts = value.split(Pattern.quote(separator), -1);
    302                 results.addAll(Arrays.asList(parts));
     300            String pattern = Pattern.quote(separator);
     301            try {
     302                for (String value: values) {
     303                    results.addAll(Arrays.asList(value.split(pattern, -1)));
     304                }
     305            } catch (NumberFormatException e) {
     306                Logging.error("Unable to parse {0} values in {1} -> {2}", sort, this, e.getMessage());
     307                Logging.debug(e);
     308                results = values;
    303309            }
    304310            return String.join(separator, results);
Note: See TracChangeset for help on using the changeset viewer.