Error highlights in Eclipse Scala

I've seen a similar problem in the 2.8 nightly build.

When I do a clean followed by an automatic build I get lots of "not found
type: ..." and "not found value: ..." error messages. The messages appear in
the editor but not in the Problems View. The strange thing is that the code
compiles and runs (all the junit test run without problems).

On Mon, Nov 23, 2009 at 3:28 PM, Spiros Tzavellas wrote:
> I've seen a similar problem in the 2.8 nightly build.
>
> When I do a clean followed by an automatic build I get lots of "not found
> type: ..." and "not found value: ..." error messages. The messages appear in
> the editor but not in the Problems View. The strange thing is that the code
> compiles and runs (all the junit test run without problems).

I've only seen this in complex scenarios with either multiple
dependent projects (symptom: spurious project-level errors) or where
early compilation failures have prevented otherwise good code from
being built which then has knock on effects on code which depends on
it (sounds like what you're experiencing).

As ever, if you're able to produce a small reproducible test case that
and attach it to a Trac ticket would be enormously helpful.

But yes, I agree, there are still issues with the new incremental
builder and presentation compiler ... moving them into scalac has
helped a lot but was never going to be a panacea.

Cheers,

Miles

Well, I do not have any project dependencies. I build all code from other
projects into a JAR per project and add those to the build path. I do have
about 75 source files in the project.
Each clean/build makes this reappear. There are no errors in the code and as
said by Spiros the code builds and runs fine.
The error highlights appear in any open source editor as soon as the clean
happens. The subsequent build does not make them go away anymore. It seems
like the editor picks up the deletion of the .class files but does not see
them being recreated.

I can reproduce this at will but hardly consider it a small reproducible
test case :-)

Regards,

Silvio

Hi Silvio,

we are talking about the same bug.

Spiros Tzavellas wrote:
>
> we are talking about the same bug.
>

So it seems. Any chance you can reproduce this with only a couple of sample
sources? I tried but to no avail...

I've already created bug 2689
(https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to
this one. I'll try again sometime tomorrow.

So far I've opened two bugs (2689 and 2680) while trying to find a small
project that accurately reproduces this bug.

On Mon, Nov 23, 2009 at 11:22 PM, Spiros Tzavellas wrote:
>
> I've already created bug 2689
> (https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to
> this one. I'll try again sometime tomorrow.
>
> So far I've opened two bugs (2689 and 2680) while trying to find a small
> project that accurately reproduces this bug.

This is great stuff, BTW, very much appreciated ... expect some
progress in the next day or so.

Cheers,

Miles

Wow, very nicely summarized :)
I've been suffering with this one too, but blaming myself (there was a certain compiler plugin involved...)
Good work that man!

On Mon, Nov 23, 2009 at 11:27 PM, Miles Sabin <miles@milessabin.com> wrote:

On Mon, Nov 23, 2009 at 11:22 PM, Spiros Tzavellas <sptz45@gmail.com> wrote:
>
> I've already created bug 2689
> (https://lampsvn.epfl.ch/trac/scala/ticket/2689) that is probably related to
> this one. I'll try again sometime tomorrow.
>
> So far I've opened two bugs (2689 and 2680) while trying to find a small
> project that accurately reproduces this bug.

This is great stuff, BTW, very much appreciated ... expect some
progress in the next day or so.

Cheers,


Miles

--
Miles Sabin
tel: +44 (0)7813 944 528
skype:  milessabin
http://www.chuusai.com/
http://twitter.com/milessabin

Hi Kevin,

I was also blaming myself :-)

then I was blaming Maven and when this problem became really painful I
decided to track it down. The only project were I couldn't reproduce this
bug is the project where I keep all the SDT bugs that I've submitted (this
might be because the classes in that project are usually not connected with
each other).

Kevin Wright-4 wrote:
>
> Wow, very nicely summarized :)
>
> I've been suffering with this one too, but blaming myself (there was a
> certain compiler plugin involved...)
>
> Good work that man!
>
>