4 ms·
Not a fundamental flaw, but took some time to figure it out once I was hit by it. Jar files are iterated in a non defined (filesystem) order, meaning if the sam
by rossmohax 5y ago
Not a fundamental flaw, but took some time to figure it out once I was hit by it. Jar files are iterated in a non defined (filesystem) order, meaning if the same class is found in more than one jar file, on 2 different systems different version of the class can be loaded.
- watwut 5y agoThis one will be somewhat better, because of those two will be in different modules they will be independent. If it happens within one module, then it stays the same. I agree that this one is annoying. It happens rarely, but every time it happens it is frustrating for whoever is dealing with it. I think there are ways how to automatically check for this, but yeah.