harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Catherine Hope (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-6321) [VM] -Xbootclasspath/a is not appended properly with IBM VMI
Date Thu, 27 Aug 2009 23:14:59 GMT

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

Catherine Hope closed HARMONY-6321.
-----------------------------------

    Resolution: Duplicate

mistakenly raised twice due to jira server error

> [VM] -Xbootclasspath/a is not appended properly with IBM VMI
> ------------------------------------------------------------
>
>                 Key: HARMONY-6321
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6321
>             Project: Harmony
>          Issue Type: Bug
>          Components: VM
>         Environment: all
>            Reporter: Catherine Hope
>            Priority: Minor
>
> Running Harmony with IBM VMI and option -Xbootclasspath/a does not produce the expected
bootclasspath, e.g.
> > java -Xbootclasspath/a:<dir> <class>
> gives the following bootclasspath (org.apache.harmony.boot.class.path property):
>     /jdk/jre/bin/default/luni-kernel.jar:/jdk/jre/bin/default/security-kernel.jar::<dir>:/jdk/jre/lib/boot/accessibility.jar:..
remaining api jars
> So the appended directory appears between the kernal jars and the api ones, instead of
at the end of the path.
> The problem does not occur with DRLVM because the bootclasspath is set up as follows:

> in the launcher
> - passes contents of harmonyvm.properties (containing luni-kernal and security jars)
and command-line arguments to CreateJavaVM
> in luniglob (called on JNI_OnLoad)
> - retrieves org.apache.harmony.boot.class.path property from VM and _appends_ the api
jars from bootclasspath.properties
> - sets org.apache.harmony.boot.class.path property to the new value
> with Harmony with IBM VM
> - org.apache.harmony.boot.class.path property contains the parsed and set bootclasspath,
api jars are added at the end
> with Harmony with DRL VM
> - org.apache.harmony.boot.class.path property is null, api jars are added and then this
value is used later by classloader.bootstrap_components_classpath to combine with the other
components and form sun.boot.class.path
> There's a difference in how the two bootclasspath properties sun.boot.class.path and
org.apache.harmony.boot.class.path are being used by DRLVM and IBM VMI - DRLVM uses the sun.boot.class.path
as the definitive one, assembled from the contents of org.apache.harmony.boot.class.path,
and IBM VMI uses the org.apache.harmony.boot.class.path completely, and sun.boot.class.path
is null.

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


Mime
View raw message