Re: Compile Problem involving Dependencies

From:

Lew <lewbloch@gmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 29 Oct 2011 17:06:43 -0700 (PDT)

Message-ID:

<31537605.902.1319933203136.JavaMail.geo-discussion-forums@prmv24>

markspace wrote:

Novice wrote:

The fresh build did the trick; all the compiler
errors went away and I was able to run the applet successfully. I like
Eclipse but it does seem to get confused sometimes; >

You're welcome. NetBeans seems to have the same problem. Periodically=

Pretty much *all* build systems have this problem.

weird errors show up and I have to do the "clean and rebuild full
project." I guess it might be common behavior related to some compiler=

API they both use, since Java has made one available for programmers a
while back.

*shrug* At least you didn't have to reach for the "big red switch."

It's common behavior to all build systems, particularly Java-esque ones tha=
t track dependencies through the .class files in the "-d" target directory =
of javac.

In the face of refactoring and certain strange scenarios, .class files rema=
in in the target directory for which either the source files have a changed=
transitive dependency or the source no longer exists or a constant is not =
deemed worthy of a recompile or what-all.

Later another class sees something in the now-no-longer-valid .class file a=
nd weirdness ensues. Finally the hapless programmer does a full "clean", a=
nd voil=E0! Problem solved.

--
Lew