Home » Language IDEs » Java Development Tools (JDT) » Java Editor shows 'class resolution' errors in Galileo
| Java Editor shows 'class resolution' errors in Galileo [message #260802] |
Thu, 25 June 2009 20:31  |
Eclipse User |
|
|
|
Hi,
After I switched from RC1 to the final release of Galileo, I'm seeing
conflicting 'class resolution' errors in the JDT.
Even though my:
- Package Explorer View
- Outline View
- Problems View
do *not* show any errors,
Any Java file I open in a Java editor shows a complete failure to find
any classes at all. The entire file is littered with error markers,
starting from the package declaration, the imports and all class references.
I have a custom classpath container, which shows up properly in the
Package Explorer View, and I can even navigate inside the package
structure there, where all the alledged missing classes are available
and shown.
Are there any late bug fixes in this area which can explain this
behaviour, as this is something that cropped up after I upgraded to the
official Galileo release.
What is remarkable is that the code *does* compile and all the existing
run targets do start their associated applications, regardless (with
class files allegedly broken in the editors).
Thanks,
Dann
|
|
|
| Re: Java Editor shows 'class resolution' errors in Galileo [message #260808 is a reply to message #260802] |
Fri, 26 June 2009 03:06  |
| Eclipse User |
|
|
|
Dann Martens wrote:
> Hi,
>
> After I switched from RC1 to the final release of Galileo, I'm seeing
> conflicting 'class resolution' errors in the JDT.
>
> Even though my:
> - Package Explorer View
> - Outline View
> - Problems View
> do *not* show any errors,
>
> Any Java file I open in a Java editor shows a complete failure to find
> any classes at all. The entire file is littered with error markers,
> starting from the package declaration, the imports and all class
> references.
>
> I have a custom classpath container, which shows up properly in the
> Package Explorer View, and I can even navigate inside the package
> structure there, where all the alledged missing classes are available
> and shown.
>
> Are there any late bug fixes in this area which can explain this
> behaviour, as this is something that cropped up after I upgraded to
> the official Galileo release.
>
> What is remarkable is that the code *does* compile and all the
> existing run targets do start their associated applications,
> regardless (with class files allegedly broken in the editors).
Check your Java build path. It looks like some indirectly referenced
types (bundles) are missing.
Dani
>
> Thanks,
> Dann
|
|
|
| Re: Java Editor shows 'class resolution' errors in Galileo [message #260818 is a reply to message #260808] |
Fri, 26 June 2009 14:41 |
| Eclipse User |
|
|
|
Hi Daniel,
If that happens (indirect references), I usually see a single error
marker at the first line of the file in the editor. The message is also
explicit on that diagnose, no?
Best regards,
Dann
Daniel Megert wrote:
> Dann Martens wrote:
>> Hi,
>>
>> After I switched from RC1 to the final release of Galileo, I'm seeing
>> conflicting 'class resolution' errors in the JDT.
>>
>> Even though my:
>> - Package Explorer View
>> - Outline View
>> - Problems View
>> do *not* show any errors,
>>
>> Any Java file I open in a Java editor shows a complete failure to find
>> any classes at all. The entire file is littered with error markers,
>> starting from the package declaration, the imports and all class
>> references.
>>
>> I have a custom classpath container, which shows up properly in the
>> Package Explorer View, and I can even navigate inside the package
>> structure there, where all the alledged missing classes are available
>> and shown.
>>
>> Are there any late bug fixes in this area which can explain this
>> behaviour, as this is something that cropped up after I upgraded to
>> the official Galileo release.
>>
>> What is remarkable is that the code *does* compile and all the
>> existing run targets do start their associated applications,
>> regardless (with class files allegedly broken in the editors).
> Check your Java build path. It looks like some indirectly referenced
> types (bundles) are missing.
>
> Dani
>>
>> Thanks,
>> Dann
|
|
|
| Re: Java Editor shows 'class resolution' errors in Galileo [message #260833 is a reply to message #260818] |
Sat, 27 June 2009 03:48 |
| Eclipse User |
|
|
|
Dann Martens wrote:
> Hi Daniel,
>
> If that happens (indirect references), I usually see a single error
> marker at the first line of the file in the editor. The message is
> also explicit on that diagnose, no?
Right. What error message do you get exactly and did you check the
bundle dependencies as I advised?
Dani
>
> Best regards,
> Dann
>
>
> Daniel Megert wrote:
>> Dann Martens wrote:
>>> Hi,
>>>
>>> After I switched from RC1 to the final release of Galileo, I'm
>>> seeing conflicting 'class resolution' errors in the JDT.
>>>
>>> Even though my:
>>> - Package Explorer View
>>> - Outline View
>>> - Problems View
>>> do *not* show any errors,
>>>
>>> Any Java file I open in a Java editor shows a complete failure to
>>> find any classes at all. The entire file is littered with error
>>> markers, starting from the package declaration, the imports and all
>>> class references.
>>>
>>> I have a custom classpath container, which shows up properly in the
>>> Package Explorer View, and I can even navigate inside the package
>>> structure there, where all the alledged missing classes are
>>> available and shown.
>>>
>>> Are there any late bug fixes in this area which can explain this
>>> behaviour, as this is something that cropped up after I upgraded to
>>> the official Galileo release.
>>>
>>> What is remarkable is that the code *does* compile and all the
>>> existing run targets do start their associated applications,
>>> regardless (with class files allegedly broken in the editors).
>> Check your Java build path. It looks like some indirectly referenced
>> types (bundles) are missing.
>>
>> Dani
>>>
>>> Thanks,
>>> Dann
|
|
|
| Re: Java Editor shows 'class resolution' errors in Galileo [message #260883 is a reply to message #260833] |
Mon, 29 June 2009 13:41 |
| Eclipse User |
|
|
|
Hi Daniel,
The bundle dependency hierarchy is simple and complete. The classes
which 'do not resolve to a type' in the editors are also available on
the classpath, as I can browse them in the package explorer through a
library node. Those library classes have no indirected references
whatsoever: the entire library is self-contained and depend only on the
usual suspects of java platform libraries.
I would like to investigate the matter a bit more, first, before
pursuing this further.
Thank you for your help,
Dann
Daniel Megert wrote:
> Dann Martens wrote:
>> Hi Daniel,
>>
>> If that happens (indirect references), I usually see a single error
>> marker at the first line of the file in the editor. The message is
>> also explicit on that diagnose, no?
> Right. What error message do you get exactly and did you check the
> bundle dependencies as I advised?
>
> Dani
>>
>> Best regards,
>> Dann
>>
>>
>> Daniel Megert wrote:
>>> Dann Martens wrote:
>>>> Hi,
>>>>
>>>> After I switched from RC1 to the final release of Galileo, I'm
>>>> seeing conflicting 'class resolution' errors in the JDT.
>>>>
>>>> Even though my:
>>>> - Package Explorer View
>>>> - Outline View
>>>> - Problems View
>>>> do *not* show any errors,
>>>>
>>>> Any Java file I open in a Java editor shows a complete failure to
>>>> find any classes at all. The entire file is littered with error
>>>> markers, starting from the package declaration, the imports and all
>>>> class references.
>>>>
>>>> I have a custom classpath container, which shows up properly in the
>>>> Package Explorer View, and I can even navigate inside the package
>>>> structure there, where all the alledged missing classes are
>>>> available and shown.
>>>>
>>>> Are there any late bug fixes in this area which can explain this
>>>> behaviour, as this is something that cropped up after I upgraded to
>>>> the official Galileo release.
>>>>
>>>> What is remarkable is that the code *does* compile and all the
>>>> existing run targets do start their associated applications,
>>>> regardless (with class files allegedly broken in the editors).
>>> Check your Java build path. It looks like some indirectly referenced
>>> types (bundles) are missing.
>>>
>>> Dani
>>>>
>>>> Thanks,
>>>> Dann
|
|
|
Goto Forum:
Current Time: Wed Jul 16 00:34:24 EDT 2025
Powered by FUDForum. Page generated in 0.05690 seconds |
Home