Lorris,
You cannot use new API in java.base in the code for javac, meaning the
java.compiler and jdk.compiler modules. This is an ingherent limitation
of the bootstrap process.
-- Jon
On 2/27/24 1:57 AM, Lorris wrote:
Yes indeed, I am trying to use those changes from the jdk.compiler
I don’t have problems with clock skew (or at least I never encountered any
problem with it until today). The problem I was referring to in this statement
is when I modify a class A, to add for example a method to it, and then
reference this new method in another file B, when I build for the
Yes indeed, I am trying to use those changes from the jdk.compiler module. How
can I make this work without causing problem when building the interim module ?
Lorris
> On 26 Feb 2024, at 14:59, erik.joels...@oracle.com wrote:
>
> Hello Lorris,
>
> This is not expected behavior. Building
On 2024-02-26 14:40, Lorris wrote:
(it seems to depend on the date of the last edited file)
Just checking: do you have a problem with clock skew on your machine, or
are you using some tools that modify time stamps on modified files? The
make machinery depends on the fact that edited files
Hello Lorris,
This is not expected behavior. Building incrementally is expected to
work correctly.
If you are making changes to java.base and then trying to use those
changes from any of java.compiler, jdk.compiler and jdk.javadoc, you
will have problems as those three modules have to be
Hello,
I’m trying to build the JDK (version 23, my fork is up to date as of
2024/02/26) while adding new source files and also adding some fields or
methods in existing files (in java.base and java.compiler modules). My problem
is that when I try to build the image, most of the time (it seems
