Looks good to me.
-phil.
On 9/12/2014 1:48 PM, Mandy Chung wrote:
With the Modular Source Code [1] in JDK 9, the verify-modules target
was added in the build to catch any regression to the module boundaries.
It's important to catch this regression early during jdk development.
This patch propos
With the Modular Source Code [1] in JDK 9, the verify-modules target
was added in the build to catch any regression to the module boundaries.
It's important to catch this regression early during jdk development.
This patch proposes to add verify-modules to the default target
and also images target
On 9/12/14 7:03 AM, Erik Joelsson wrote:
Hello,
The checked in modules.list file defines the dependencies between
modules for the build. The dependency information in this file is
already captured in the modules.xml. Rather than keeping two copies of
this information, with this change, module
Hi Erik:
The checked in modules.list file defines the dependencies between
modules for the build. The dependency information in this file is
already captured in the modules.xml. Rather than keeping two copies of
this information, with this change, modules.list is generated during
the build.
Looks good to me as well.
Tim
On 09/12/14 08:17, Erik Joelsson wrote:
Hello Erik,
Looks good to me. Don't forget to also push the generated-configure.sh
files.
/Erik
On 2014-09-12 17:05, Erik Helin wrote:
Hi all,
the top-level Makefiles are using the target jvm in the HotSpot
Makefiles
Hello Erik,
Looks good to me. Don't forget to also push the generated-configure.sh
files.
/Erik
On 2014-09-12 17:05, Erik Helin wrote:
Hi all,
the top-level Makefiles are using the target jvm in the HotSpot
Makefiles when configured with --debug-level=slowdebug. The jvmg
target has been d
Hi all,
the top-level Makefiles are using the target jvm in the HotSpot
Makefiles when configured with --debug-level=slowdebug. The jvmg target
has been deprecated in the HotSpot Makefiles, the debug target should be
used instead.
This small patch changes jdk-options.m4 to use the debug targ
Hello,
The checked in modules.list file defines the dependencies between
modules for the build. The dependency information in this file is
already captured in the modules.xml. Rather than keeping two copies of
this information, with this change, modules.list is generated during the
build.
C
