facebook

Smoothing the Transition to Yosemite (OSX 10.10)

With the release of Yosemite, the newest Mac OS update, 32-bit Java is thrown out the door. For those developing with 32-bit Eclipse on Mac machines, this becomes a troublesome issue. SDC 2015 offers the best path for a painless transition to Yosemite. This document outlines the steps to ensure your SDC-managed Eclipse and MyEclipse installations transition smoothly during an update to Yosemite.

  • Learn about the issues around 32-bit Eclipse and Yosemite
  • See how SDC can help
  • Get practical steps for a smooth transition

Read More

Duration Time: 30 Minutes

Start Tutorial Now

Don't have SDC? Download Now

Issues with 32-bit Eclipse and Yosemite

As part of the Yosemite update, 1.6 JVM and older is removed from the system. Your 32-bit Eclipse and all uninstallers need this JVM to run. You can continue running Eclipse 32-bit by reinstalling the legacy 1.6 JVM, though this is a manual process. However, if you don’t switch to 64-bit Eclipse, you will continue to have this issue with each update of your Mac OS.

SDC Smoothes the Upgrade Experience

If you have not yet upgraded to Yosemite, Secure Delivery Center makes the update less painful for Eclipse users whose software is managed by SDC. SDC 2015 recognizes users running a 32-bit installation and offers to migrate their software to 64-bit. In addition, updating packages in SDC 2015 generates 64-bit uninstallers so software removal is available, if necessary.

Secure Delivery Center 2015 also recognizes if a system is missing a 1.7+ JVM and prompts users to acquire and install this required software. By migrating to 64-bit Eclipse and ensuring the correct JVM is installed prior to the Yosemite update, your Eclipse will be ready to go once Yosemite is in place.

Preparing for Yosemite (or Fixing Eclipse Installations Post-Yosemite)

To prepare your Eclipse installations for Yosemite, follow the recommendations outlined below. If you already upgraded to Yosemite without first preparing your SDC-managed Eclipse installations, you might find yourself inundated with support calls from users whose 32-bit Eclipse will not run. The steps below will get Eclipse users running again.

  1. Update your hub to SDC 2015.
    update_hub
    Updating delivery hub
  2. Promote packages so in-product updates that repair uninstallers are available to 64-bit users.
  3. Rebuild your package installers for all packages that include a Mac OSX installer. The new installers and uninstallers will be 64-bit.
  4. Users who haven’t yet updated to Yosemite: Accept the update to the latest Eclipse version. Those using 32-bit are prompted to switch to 64-bit.
    switch_to_64_notification
    Switch to 64-bit notification
    Users who have already updated to Yosemite: 32-bit users should run the new installers and accept the auto migration to 64-bit Eclipse when prompted.
    installer_switch_64
    Migration to 64-bit
    Note: 64-bit users can simply accept the in-product update.
  5. Have all Mac users install the recommended 1.7+ JVM, if prompted.
    java_required
    Missing required JVM notificationIf the required JVM is bundled with the package or 1.7+ JVM is present on the system, this prompt will not appear.

After these steps are completed, your Eclipse installations are ready to run on Yosemite.

Known Issues

Eclipse 4.3.1 and older packages prompting for Java 1.6 when deployed to Mac OSX
This is a shortcoming in the older Eclipse launchers, which cannot find the modern location of the JRE installed on Mac OSX. To fix this issue, include a JRE with your package, and the package will launch with no problems. 

Fix – Include a JRE with your package, and the package will launch with no problems.