On 10/06/15 16:30, Erik Joelsson wrote:
On 2015-06-10 15:25, Maurizio Cimadamore wrote:
Hi,
In the context of the IntelliJ project support for JDK, I have a
question on the very last step of 'make images' :
## Starting verify-modules
Checking dependencies across JDK modules
Access verification succeeded.
I noticed that this step is always applied, regardless of whether
there was actually any change in the sources/built classes or not. Is
that deliberate? This is a bit unfortunate as in our setup we depend
on 'make images' to run tests, and if there's nothing to do, you will
still have to wait several seconds for 'make images' to complete.
You are not alone in finding it annoying. It was added to the images
target to force it to be run often. We will stop running it when the
module system is properly in place and can verify this implicitly at
compile time. Unconditionally running it when nothing has changed
could be fixed and would help in some situations. A workaround is to
run "make jimages", which is usually what you want anyway and then
following that with "make test-only" which bypasses the dependency on
images.
Ok thanks for the tip, I will try that.
Maurizio
/Erik
Maurizio
