Handling Old .jar Files: Difference between revisions
(Creating article) |
No edit summary |
||
Line 1: | Line 1: | ||
When handling old .jar files, it is important to not just rename the files, but also to move them out of the directory. Due to Java class loading rules, every file in a directory is loaded. This can create class loading problems if old .jar files are still in the same directory as the current .jar file. To ensure that old .jar files are not loaded, move them to another directory. | {{Archive}}When handling old .jar files, it is important to not just rename the files, but also to move them out of the directory. Due to Java class loading rules, every file in a directory is loaded. This can create class loading problems if old .jar files are still in the same directory as the current .jar file. To ensure that old .jar files are not loaded, move them to another directory. | ||
Latest revision as of 12:44, 24 March 2015
- This is archive documentation, which means it is not supported or valid for recent versions of Zimbra Collaboration.
When handling old .jar files, it is important to not just rename the files, but also to move them out of the directory. Due to Java class loading rules, every file in a directory is loaded. This can create class loading problems if old .jar files are still in the same directory as the current .jar file. To ensure that old .jar files are not loaded, move them to another directory.