Revision as of 01:47, 3 January 2012 edit Hervegirod (talk \| contribs) Autopatrolled, Extended confirmed users 15,455 edits fix formatting ← Previous edit		Revision as of 21:11, 31 January 2012 edit undo Naviguessor (talk \| contribs) Extended confirmed users 7,051 edits m →JAR hell Next edit →
Line 82: The [[OSGi]] Alliance specified (starting as JSR 8 in 1998) a modularity framework that solved JAR hell for current and future VMs in ME, SE, and EE that is widely adopted. Using metadata in the JAR [[manifest file\|manifest]], JAR files (called bundles) are wired on a per-package basis. Bundles can export packages, import packages and keep packages private, providing the basic constructs of modularity and versioned dependency management. To remedy the JAR hell problems a [[Java Community Process]] — JSR 277 was initiated in 2005. The resolution — [[Java Module System]] — intended to introduce a new distribution format, a modules versioning scheme, and a common modules repository (similar in purpose to [[Microsoft .NET]]'s [[Global Assembly Cache]]). In December 2008 Sun announced that JSR 277 was put on hold.<ref>http://www.osgi.org/News/20081217</ref> == See also ==

Java class loader: Difference between revisions