It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Java class loader" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Java class loader|concern=Virtually no context, earlier speedy was removed by author. Time given for improvement, but page has been static since 1 Nov.}} ~~~~Timestamp: 20061113081714 08:17, 13 November 2006 (UTC) Administrators: delete |
JAR Hell usually occurs when a class file located in a JAR file can not be found or an older version from another JAR file is loaded. Common causes are wrong packaging of the application, wrong configuration of the classpath(s), lack of understanding of the java class loading model, assuming that an application will be the only one running on a server and faulty design.
Its usually worsened by the tendency to add even more JAR files to different directories in the hope of resolving a ClassNotFoundException or a NoClassDefFoundError.
External Links
http://krysalis.org/version/jar-hell.html http://www.jcp.org/en/jsr/detail?id=277