harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-1626) [drlvm] ineffective bootclasspath detection
Date Fri, 06 Oct 2006 09:15:21 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1626?page=all ]

Geir Magnusson Jr updated HARMONY-1626:

    Attachment: HARMONY-1626-proposed.diff

Here's my proposed solution - we wait until luni has been initialized, and then take the classpath
from there, tacking on kernel.jar

This also includes the change so that kernel.jar lives in bin/<vmdir> with the rest
of the DRVM artifacts for cleaner deployment

> [drlvm] ineffective bootclasspath detection
> -------------------------------------------
>                 Key: HARMONY-1626
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1626
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Alexey Varlamov
>            Priority: Minor
>         Attachments: HARMONY-1626-proposed.diff, props2.diff
> The DRLVM duplicates parsing of "bootlclasspath.properties" after luni natives loading,
and does this quite ineffectively, by reading single symbol at a time.
> Accordingly to VMI, bootclasspath should be composed by "hyluni" library and made available
to VM via "org.apache.harmony.boot.class.path" property.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message