Ticket #252 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

VM-specific options should only conditionally be inserted to eclipse.ini

Reported by: stephan Owned by: stephan
Priority: critical Milestone: OTDT_1.3.0_M3
Component: provisioning Version: 1.3.0M2
Keywords: Cc:

Description

Currently we are adding two options to eclipse.ini that are specific to the Sun JVM: -XX:+UnlockDiagnosticVMOptions and -XX:+UnsyncloadClass.

It appears that these options may cause a failure to launch the OTDT on MacOS, although normally the JVM should simply ignore any -XX options which it cannot understand.

workaround: manually delete these options from eclipse.ini after installing the OTDT.

Obviously, these options shouldn't be added to eclipse.ini in the first place when running on a platform other than the Sun JVM. Thus we need to investigate if such conditional actions are possible using p2.

Change History

Changed 3 years ago by stephan

  • status changed from new to closed
  • resolution set to fixed

Attempted workaround is in r21610:

  • after asking on the equinox newsgroup let's use a dual strategy:
    • promote the introduction of conditional touchpoint actions (not supported yet)
    • avoid the problem by an os-specific fragment

The new fragment org.objectteams.otequinox.sunjvm is installed only on these operating systems:

  • linux
  • win32
  • solaris

I am assuming that on those OS's the SunJVM might be used -> install the Sun-specific vm-flags. On other OS's don't. Other than its MANIFEST.MF and p2.inf this fragment is empty.

Changed 3 years ago by stephan

  • priority changed from major to critical
Note: See TracTickets for help on using tickets.