On Tue, Oct 28, 2014 at 11:40:49AM +0100, Erik Joelsson wrote:
> Hello,
>
> Please review this small fix when using sjavac. When using a bootjdk
> that was built at a later date than when the source tree was
> initially cloned, there is a risk that sjavac will pick up classes
> from the boot class
Why is sjavac ever looking at the classes in the bootclasspath of the
boot jdk in the compilation environment?
The boot JDK should only be used to *run* sjavac. Nothing more. The
compilation environment should only be "the new world".
-- Jon
On 10/28/2014 03:40 AM, Erik Joelsson wrote:
Hell
Hi Erik,
Looks good.
As the comment says source only wins over a newer classfile from
bootclasspath, usually rt.jar of the building jdk. A newer classfile in
the build destination that were compiled in a previous compile won't
trigger a recompile.
cheers
/Joel
On 2014-10-28, Erik Joelsson wrote
Hello,
Please review this small fix when using sjavac. When using a bootjdk
that was built at a later date than when the source tree was initially
cloned, there is a risk that sjavac will pick up classes from the boot
classpath (rt.jar of boot jdk) instead of the source files, concluding
that
