images

[Jonathan Gibbons]

Mandy,

Thanks.   Given an image, how can I tell what is in it?  Are there 
techniques that do not directly use jigsaw APIs?  For example, if jtreg 
is running on top of JDK 1.6, and is asked to run tests using a JDK 1.7 
image, can it look at the image to determine what classes are available?

-- Jon


Mandy Chung wrote:
> Jonathan Gibbons wrote:
>> Mandy,
>>
>> Can you give a brief summary of all the (new) images made by "make 
>> modules"?
>> -- Jon
>>
>>> $ ls -d1 build/*/*image
>>> build/linux-amd64/j2re-image
>>> build/linux-amd64/j2sdk-image
>
> These two are legacy JRE and JDK images.  They are not built by the 
> "modules" target.
>
>> build/linux-amd64/jre-base-image 
> jre-base-image is the minimal Java runtime only with jdk.boot and 
> jdk.base modules installed
>
>> build/linux-amd64/jdk-base-image 
>
> jdk-base-image is jre-base-image with the language tools including 
> javac, javah, javap, and javadoc.  This is convenience for running 
> tests for the base image that needs javac to compile.
>
>>> build/linux-amd64/jdk-module-image
>
> Full JDK (equivalent to j2sdk-image)
> i.e. jre-module-image + all other jdk modules installed (e.g. all 
> tools, debugging, hprof, etc).
>
>>>
>>> build/linux-amd64/jre-module-image
>>
> Full Java runtime environment with all JRE modules installed 
> (equivalent to j2re-image)
>
> The new module images output by the "modules" target are also 
> described in jdk/make/common/Modules.gmk.
>
> The modules target also generates jdk modules in:
> build/linux-amd64/jigsaw-pkgs/[jmod, deb]
>  - all jdk modules are packaged in jmod file format under the jmod 
> directory
>  - if building on debian systems, debian packages are created under 
> the deb directory.
>
> Alan has hacked up a quick tool to generate the javadoc for each of 
> the modules.   Before the javadoc becomes module-aware, it would be 
> useful to post the per-module javadoc for reference.
>
> Mandy