and refactor other code accordingly. Do not forgot about Libraries Node.
BTW I recently added hashCode for some classes with equals, acc. to FindBugs;
hope it was correct.
Surely not :). I just think I misunderstand some concepts in the beginning so I
presumably caused a little mess on some places which use ModuleDependencies
(mainly in the GUI).
test/unit/ui/customizer/ModuleDependencyTest.java; 1.3 -> 1.4;
ProjectXMLManager.java; 1.44 -> 1.45;
ui/LibrariesNode.java; 1.7 -> 1.8;
ui/customizer/ModuleDependency.java; 1.19 -> 1.20;
ui/customizer/SingleModuleProperties.java; 1.53 -> 1.54;
Forgot mark as fixed.
Backported into 5.0u1
project/ProjectXMLManager.java; 1.44 -> 184.108.40.206;
project/ui/customizer/ModuleDependency.java; 1.19 -> 220.127.116.11;
project/ui/customizer/SingleModuleProperties.java; 1.53 -> 18.104.22.168;
project/test/unit/ui/customizer/ModuleDependencyTest.java; 1.3 -> 22.214.171.124;
project/ui/LibrariesNode.java; 1.7 -> 126.96.36.199;
Note this was actually bug (and/or allows to fix another one)
Note: as part of issue #72463 I will discard most of this, so that MD instances
are compared and sorted only by code name base. This is not mathematically
accurate but I think it doesn't matter - AFAIK there will never be two MD's with
the same code name base in one set at once. And supporting lazy evaluation of
the specification version while retaining mathematical correctness is just not
possible. Review will be requested.