Re: Compiler incompatibility?
- From: "Rhino" <no.offline.contact.please@xxxxxxxxxx>
- Date: Sat, 29 Apr 2006 19:12:30 -0400
Just to update anyone following this thread, I have solved the problem,
although I'm not quite sure why this solution worked.
First, I tired making a trivial change to the source of Bar, the class I was
depending on, to force Eclipse to recompile it. The recompile worked and the
date on the .class file was updated but the compile of Foo failed on the
same error.
Then, I tried deleting the .class file for Bar just to see what would
happen. I expected to have to recompile Bar to create the .class file but I
tried the compile of Foo, just for laughs, with the Bar.class file no longer
in existence. Much to my surprise, the compile of Foo worked fine!
Also, a new copy of Bar.class wound up in the directory where it was
supposed to be, even though I had deleted the old Bar.class and had NOT
recompiled the source. Or maybe I should say I didn't force it to recompile
in Eclipse! My Javac task in Ant somehow figured out that Bar.java needed to
be recompiled and did it for me and, since both Bar and Foo were compiled by
the Ant javac compiler this time, they were both compatible and the compile
of Foo worked.
--
Rhino
.
- References:
- Compiler incompatibility?
- From: Rhino
- Re: Compiler incompatibility?
- From: Jean-Francois Briere
- Re: Compiler incompatibility?
- From: Rhino
- Compiler incompatibility?
- Prev by Date: Re: Incorrect "variable might not have been initialized"
- Next by Date: Re: TableSorter.java v2.1
- Previous by thread: Re: Compiler incompatibility?
- Next by thread: Eclipse: Checkstyle error indicators not updating when I save the file
- Index(es):
Relevant Pages
|