Fix semantics of cgeo.geocaching.utils.CollectionUtils.isEmpty()

The two instances of isEmpty() are obviously wrong with regards to the
null pointer. Right now, a null pointer is considered neither empty nor
not-empty. The error shows up in commit 53936c7ee6654a525075b03e1b4c8ddbfbcd4ef5
introducing CollectionUtils where

  logCounts == null || logCounts.isEmpty()

has been changed into

  CollectionUtils.isEmpty(logCounts)

A null logCounts variable would make the condition evaluate to false
while it should evaluate to true.

The logical flow for isEmpty(List<T> list) found at cgeomaps.java:34 shows
that an empty "maps" variable will cause a null pointer exception in the
subsequent for loop of the else clause.

The one for isEmpty(Map<T, T2> map) found at cgData.java:1635 exhibits
the same behaviour.

0 files changed, 0 insertions, 0 deletions