-
Story
-
Resolution: Done
-
Major
-
2.3.0.Final
-
None
-
None
-
None
On Windows automatic ruleset updating is blocked by JVM keeping the .jar file open (by the class loader).
We need to come up with another implementation or use Forge's way to do it.
(17:46:26) LincolnThree: mbriskar: you can't delete files that are "in use" on windows
(17:46:57) LincolnThree: mbriskar: but since the XML rulesets are not "in use" unless we are loading them, it's not a conflict
(17:47:33) mbriskar: lincolnthree, every .class file in classpath is "in use" ?
(17:48:12) LincolnThree: mbriskar: well, most classes are in .jar files
(17:48:24) LincolnThree: mbriskar: and those .jar files are typically loaded by a ClassLoader with an open filehandle, eys
(17:48:25) LincolnThree: yes
(17:48:45) LincolnThree: mbriskar: and in Java, there is no real way to close a ClassLoader (except in furnace, because we hacked the JDK)
(17:49:34) LincolnThree: mbriskar: but, since furnace can hot-load addons anyway, update shouldn't be a problem for addons
(17:49:36) LincolnThree: mbriskar: furnace takes care of that
(17:49:43) LincolnThree: mbriskar: no need to update bootstrap, most of the time
(17:50:05) LincolnThree: mbriskar: so in reality, our dist-update should be fairly straight forward as well
- relates to
-
WINDUP-701 Fix ruleset updating
- Closed