Bentobox: Java 11 - ConcurrentModificationException with 1.2.0 update

[SlimeDog]

```[07:52:08] [Server thread/INFO]: [BentoBox] Enabling BentoBox v1.2.0
md5-82ffa721a75ddb07a2d5829bab7b8c44

bentobox version
```

[Lmmb74]

This bug only happens when using Java 10 & 11. BentoBox works fine when using Java 8. (I didn't try using Java 9 and it's a Non-LTS version so I guessed it was not worth trying [despite the fact that I tried Java 10 also being Non-LTS :V]).

[SlimeDog]

That's nice. But I am using Java 11. Please adjust appropriately, and many thanks.

[tastybento]

I'll have a look at it and see if it's something easy to fix.

[Poslovitch]

Fixing this is fine, but I definitely plan to move to Java 11 soon. The more time passes, the more I regret to not be able to use some of the features that were brought in Java 9, 10 and 11.

[tastybento]

Maybe, but when you look at the stats of what the servers use, you'll see it's 95% Java 8 still.

[Poslovitch]

Yep, but they won't move to Java 11 if not a single plugin incites them to.

[SlimeDog]

I'm all in favor, but please be aware that -- similar to servers still running Spigot 1.8.x and etc. -- that many plugins -- the entire Citizens/Denizen/Depenizen/Sentinel cluster, for example -- claim to still rely on Java 8. And many server operators do not have a choice, since they are beholden to service providers for their stacks. So, it's tricky.

Despite the fact that Java 11 and Spigot 1.13.x have been available since ... never mind. :)

[SlimeDog]

Among the minor issues here, the addons were not successfully enabled, as claimed in the log.

[tastybento]

This should be fixed for now.

[SlimeDog]

Confirmed fixed in BentoBox 1.2.1
No more ConcurrentModificationException with Java 11