You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2007/05/21 14:58:16 UTC

[jira] Updated: (HARMONY-3565) [testing][eclipse] eclipse intermittently failed to compile "Hello world" class

     [ https://issues.apache.org/jira/browse/HARMONY-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Shimansky updated HARMONY-3565:
---------------------------------------

    Assignee: Gregory Shimansky

Trying to reproduce the problem I found out that running ecj as java -jar ecj.jar <some class> always gives an error that j.l.Object cannot be resolved. Specifying harmony boot classes explicitly with -bootclasspath for compiler makes it successfully compile the class.

Looking at CC reports I see that all self hosting errors come from building working_jdktools classes. For me the failure to find j.l.Object class is not intermittent. It is either an error in 100% cases or it doesn't exist. I suspect that ecj just doesn't correctly understand harmony java.boot.class.path property to find necessary jar files.

> [testing][eclipse] eclipse intermittently failed to compile "Hello world" class
> -------------------------------------------------------------------------------
>
>                 Key: HARMONY-3565
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3565
>             Project: Harmony
>          Issue Type: Bug
>          Components: App-Oriented Bug Reports
>            Reporter: Vladimir Ivanov
>         Assigned To: Gregory Shimansky
>         Attachments: screenshot-1.jpg
>
>
> eclipse 3.1 intermittently (1 time for ~100 runs) failed to compile "Hello world" class with message that java.lang.Object is missed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.