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/16 14:58:16 UTC

[jira] Updated: (HARMONY-2053) [classlib][port][luni] move port_user_timezone() from DRLVM to classlib

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

Gregory Shimansky updated HARMONY-2053:
---------------------------------------

    Summary: [classlib][port][luni]  move port_user_timezone() from DRLVM to classlib  (was: [port][classlib][luni]  move port_user_timezone() from DRLVM to classlib)

> [classlib][port][luni]  move port_user_timezone() from DRLVM to classlib
> ------------------------------------------------------------------------
>
>                 Key: HARMONY-2053
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2053
>             Project: Harmony
>          Issue Type: Task
>          Components: Classlib, DRLVM
>            Reporter: Alexey Varlamov
>            Priority: Minor
>
> Classlib's j.u.TimeZone expects "user.timezone" property value initialized during VM startup (BTW I did not find explicit statement in VMI docs for that, only indirect reference in kernel stub for j.l.System). I believe this action should be done by hyluni natives during JNI_OnLoad, no reason to burden VM with it. Therefore I suggest to move "port_user_timezone()" function [1] from DRLVM to classlib (luni/port), and fix DRLVM & hyluni accordingly. 
> [1] working_vm\vm\port\src\misc\[win|linux]\timezone.c 

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