Incremental compile sometimes does not recompile all indirected impacted classes

Em Mon, 14 Jun 2004 23:38:14 +0400, Jacques Morel escreveu:

Has anybody else experienced problems with classes that did get recompiled
after one dependency changed?

Never had this problem, but the inverse sometimes happens to me: IDEA
recompiling the same classes after every make, even when nothing changed.

--
Marcus Brito <pazu@animegaiden.com.br>

indirectly impacted classes ;-(

Never had them - neither in our 2000 classes nor the 3500 classes
project. Ctrl-F9 works like a charm.

Tom

Are you using multiple modules?
It may not be a factor because some coworkers have been complaining about this in 4.0 as well.

Jacques

Are you using multiple modules?

Yes, both projects use multiple modules - up to 45 modules.

Tom

I experienced the same, but rather once a month only...

So let's find out when exactly it happens ... ;)

I've seen this also, only when using multiple modules. Does anyone know a
quick and reliable way to get everything in synch again?

David

"Thomas Singer (MoTJ)" <idea@NOregnisSpam.de> wrote in message
news:cal3p4$eno$1@is.intellij.net...

Are you using multiple modules?

>

Yes, both projects use multiple modules - up to 45 modules.

>

Tom

I've seen it once, a while ago, but couldn't reproduce it.
http://www.intellij.net/tracker/idea/viewSCR?publicId=31288

Andrei

JM> Has anybody else experienced problems with classes that did get
JM> recompiled after one dependency changed?
JM>
JM> Running tests in IDEA sometimes lead to ClassCastException or
JM> NoSuchMethodException because something is out-of-date.
JM>
JM> It is rather elusive to pin down but in a day of work I will get it
JM> 2 or 3 times. I then have to rebuild the whole project which
JM> unfortunately takes a while.
JM>
JM> Jacques
JM>

Jacques Morel wrote:

Has anybody else experienced problems with classes that did get
recompiled after one dependency changed?

Yup - got that one as well. Small project (<50 classes), split into two
modules. I make changes in one module, and the other one doesn't
'notice' them. Every now and then, running the project uses stale
classes as well...
Rebuild all always fixes it (obviously), but it's still strange &
unpredictable.

CU,
Edwin