> On Nov 25, 2015, at 2:27 AM, Alan Bateman <[email protected]> wrote: > > I think we touched on this in your other thread where you used the build > <build-output>/jdk tree rather than <build-output>/images/jdk.
Sorry, you are correct on this. Once I had correctly built the images version the modules are no longer individual/exploded. I notice there are three images when built from source… appmodules.jimage bootmodules.jimage extmodules.jimage For the jake ea version I downloaded from the URL provided at the talks there is only bootmodules.jimage if that matters. Copying the other two images into the embedded application jdk still does not seem to launch. Although even command line showed that it should get the internals error. It might be the same problem for the app and I’m just not seeing the more meaningful error messages. Is there any way around the internals for a non-modularized application? A fair percentage of OS X applications might have these particular ‘internals’. There is JEP 272 so if I just wait, and change some code, that should go away. But in general, if you have other applications looking to migrate to 9 that have any of these who want to start out by just getting their application up and running they are not going to work. They will be forced to either eliminate the internal use or go modular from the start? Then the addExports will work. If I’m understanding that error message correctly. Michael Hall
