mirror of
https://github.com/openjdk/jdk.git
synced 2025-08-27 06:45:07 +02:00
8197532: Re-examine policy for the default set of modules when compiling or running code on the class path
Reviewed-by: jlahoda, mchung
This commit is contained in:
parent
6e0bd36f42
commit
7523687071
12 changed files with 363 additions and 83 deletions
|
@ -1,5 +1,5 @@
|
|||
/*
|
||||
* Copyright (c) 2013, 2017, Oracle and/or its affiliates. All rights reserved.
|
||||
* Copyright (c) 2013, 2018, Oracle and/or its affiliates. All rights reserved.
|
||||
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
|
||||
*
|
||||
* This code is free software; you can redistribute it and/or modify it
|
||||
|
@ -154,8 +154,9 @@
|
|||
* application module specified to the 'java' launcher. When compiling code in
|
||||
* the unnamed module, or at run-time when the main application class is loaded
|
||||
* from the class path, then the default set of root modules is implementation
|
||||
* specific (In the JDK implementation it is the module "java.se", if observable,
|
||||
* and every observable module that exports an API). </p>
|
||||
* specific. In the JDK the default set of root modules contains every module
|
||||
* that is observable on the upgrade module path or among the system modules,
|
||||
* and that exports at least one package without qualification. </p>
|
||||
*
|
||||
* <h2> Observable modules </h2>
|
||||
*
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue