You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Ivan Popov (JIRA)" <ji...@apache.org> on 2007/07/02 15:10:05 UTC

[jira] Updated: (HARMONY-2894) [jdktools][jdwp] JDWP agent uses non-standard VM property

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

Ivan Popov updated HARMONY-2894:
--------------------------------

    Attachment: H2894_jdwp_agent.patch

I'm attaching patch 'H2894_jdwp_agent.patch' for bootclasspath issue in JDWP agent. With this patch agent attempts to get bootclasspath value from the following system properties sequentially:

  sun.boot.class.path
  vm.boot.class.path
  org.apache.harmony.boot.class.path

Now affected JDWP test org/apache/harmony/jpda/tests/jdwp/VirtualMachine/ClassPathsTest works well for all DRLVM, IBM VME and RI. This patch also removes this test from exclude list.


> [jdktools][jdwp] JDWP agent uses non-standard VM property
> ---------------------------------------------------------
>
>                 Key: HARMONY-2894
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2894
>             Project: Harmony
>          Issue Type: Improvement
>          Components: JDK
>            Reporter: Ivan Popov
>            Priority: Trivial
>         Attachments: H2894_jdwp_agent.patch
>
>
> Current implementation of JDWP agent uses "vm.boot.class.path" VM property for returning bootclasspath value in VirtualMacnine.ClassPath command. This property is provided only in DRLVM. It makes sense to check also "sun.boot.class.path" property which is de-facto provided by most other JVMs. This will improve usability of Harmony's JDWP agent running with different JVMs.

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