Barry Evans
Barry Evans
There have been many changes in this are so I've closed this after fixing the Status Log last night.
I want to simplify the ```Loggable``` interface and drop the coordinate and container methods. I want to replace it with a new getContext method that returns a String that provides...
No coordinates will still be shown but they will be in the context
@mokun I have started looking at this. I am going to rename```Entity``` to ```NamedEntity``` and then delete ```Loggable```. The new ```NamedEnitity``` will then be used as the seed for logging....
It's good practice to only add code when it is needed. Otherwise the projects end up having a lot of unused code which leads to unwanted technical debt. Do it...
Wow, the use of our logging framework is very inconsistent. The simlogger has grown too much with way too many overlapping methods. I have just gone through and cleaned it...
There is no simple single answer. Each case needs understanding why it is occurring and what can be done. The enter airlock case is because the person will keep trying...
Release 3.5.0 will work on Java 20
OK, the problem is in the ```SettlementBuilder``` and ```Resupply``` when adding new arrival. I'll tackle it.
I'm going to close this as loading in parallel will cause more problems than it solves.