I'm certainly keen to see interoperability between the two solutions. It would be perverse for Jigsaw to introduce fundamental problems for OSGi, which is after all the current de facto standard Java module system.
(Backgound: we are using OSGi to help structure our port of General Electic's Smallworld product line to the JVM. We are intending to map Smallworld's own module system, which is specific to the Magik programming language, to OSGi bundles and probably ultimately Jigsaw modules. http://www.infoq.com/news/2012/12/magik-jvm-port ) Yours, George -----Original Message----- From: jigsaw-dev [mailto:[email protected]] On Behalf Of Neil Bartlett Sent: 30 July 2014 12:38 To: [email protected] Subject: Jigsaw/OSGi interoperability requirements Hello, I asked the following question at the beginning of July when the re-relaunch of Jigsaw was announced, but didn’t get a response. Probably it was unintentionally overlooked with all the other traffic, but I would very much appreciate an answer so I’ll ask again: The previous draft requirements dated 19 April 2011 (“Draft 12”) stated the following with respect to OSGi: “It must be demonstrated by prototype to be feasible to modify an OSGi micro-kernel such that OSGi bundles running in that kernel can depend upon Java modules. The kernel must be able to load Java modules directly and resolve them using its own resolver, except for core system modules. Core system modules can only be loaded using the module system’s reification API.” Can you confirm that this requirement will still apply in the new phase, or has it been deliberately dropped? Regards, Neil
