function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Travis JohnstonTravis Johnston 

Force.com not installing properly Mac Siera

Some background info:
  • Using instructions here: https://developer.salesforce.com/docs/atlas.en-us.eclipse.meta/eclipse/ide_install.htm
  • Java SDK version 9, tried with 8
  • Eclipse Mars 2 Release 4.5.2
  • Mac Sierra
It took a long time just to get Eclipse to open.. kept crashing after selecting a workspace. I tried Neon 3 and it would never work, so Mars 2 was the next best option. 

I go through the installation steps and use the repo for eclipse45, also tried eclipse42, and I select the main Force.com IDE option and the installation runs through fine and I restart. After restarting, the Force.com option appears in the Perpective list if I choose "Other" but it doesn't apply. 

Clicking New > Project > Java/Other Project and choosing Force.com gives a ton of errors. Most common one is:

The selected wizard could not be started.
Plug-in com.salesforce.ide.ui was unable to load class com.salesforce.ide.ui.wizards.project.ProjectCreateWizard.
An error occurred while automatically activating bundle com.salesforce.ide.ui (562).


I've tried using the -clean arg to open a fresh eclipse, no change. I've also tried going to the plugins folder to see if I could delete the com.salesforce plugin but there are none! So clearly that is the issue but I don't see how to fix it. 

I've included a screenshot of the error log. Clearly no Force.com things can be read, and are unavailable. I've tried running an update, doesn't change anything.

Screenshot of the error log shown in eclipse
Best Answer chosen by Travis Johnston
Alain CabonAlain Cabon
Hi Travis,

Force IDE (even Force IDE2, still beta) could be discontinued (the current version of Salesforce is 41 and you are installing v37-38).

This Eclipse Force IDE is slow and (quite) buggy as you have noticed.

You should use other IDEs like MavensMate + Sublime (very rapid) or Visual Studio Code (yes, it is Microsoft but it is free and even ... open source).

Lightning Components can be built using the Developer Console, or as you get more advanced, you might want to use the Force IDE, Sublime Text, MavensMate, or Visual Studio Code. 
https://trailhead.salesforce.com/fr/projects/workshop-lightning-programmatic/steps/programmatic-step-4

"As we mentioned in our last post, MavensMate will no longer be supported going forward. In his farewell message, MavensMate creator Joe Ferarro suggested users check out the Visual Studio Code Extension Pack for Salesforce DX. At the time of writing there are over 5,000 installs of the extension but no reviews so we thought we’d do a little write up."
https://bluecanvas.io/2017/09/13/salesforce-dx-visual-studio-code.html

The expert Philippe Ozil (EMEA Developer Evangelist) preferably uses Visual Studio Code now under DX (that is the future according him).
I learnt that during the Lightning Tour in Paris. Marcus Torres, Senior Director of Product Management at Salesforce focused on Lightning Components was also in Paris during this Lightning Tour.

https://developer.salesforce.com/blogs/developer-relations/2016/05/meet-new-emea-developer-evangelists.html

All Answers

Travis JohnstonTravis Johnston
Updates on some new things I have tried with no luck:
  • Uninstall Force.com and reinstall
  • Install version 37 vs 38
  • Downloaded some source code for the plugins at https://github.com/forcedotcom/idecore, but no jar files. Tried just placing the folders in the Eclipse plugins folder and restarting Eclipse. Tried installing via local and using the idecore folder, doesn't work
  • Tried going to the Eclipse market place and downloading Force.com there, well installing from there, does nothing.
Why is this so difficult.. 
Alain CabonAlain Cabon
Hi Travis,

Force IDE (even Force IDE2, still beta) could be discontinued (the current version of Salesforce is 41 and you are installing v37-38).

This Eclipse Force IDE is slow and (quite) buggy as you have noticed.

You should use other IDEs like MavensMate + Sublime (very rapid) or Visual Studio Code (yes, it is Microsoft but it is free and even ... open source).

Lightning Components can be built using the Developer Console, or as you get more advanced, you might want to use the Force IDE, Sublime Text, MavensMate, or Visual Studio Code. 
https://trailhead.salesforce.com/fr/projects/workshop-lightning-programmatic/steps/programmatic-step-4

"As we mentioned in our last post, MavensMate will no longer be supported going forward. In his farewell message, MavensMate creator Joe Ferarro suggested users check out the Visual Studio Code Extension Pack for Salesforce DX. At the time of writing there are over 5,000 installs of the extension but no reviews so we thought we’d do a little write up."
https://bluecanvas.io/2017/09/13/salesforce-dx-visual-studio-code.html

The expert Philippe Ozil (EMEA Developer Evangelist) preferably uses Visual Studio Code now under DX (that is the future according him).
I learnt that during the Lightning Tour in Paris. Marcus Torres, Senior Director of Product Management at Salesforce focused on Lightning Components was also in Paris during this Lightning Tour.

https://developer.salesforce.com/blogs/developer-relations/2016/05/meet-new-emea-developer-evangelists.html
This was selected as the best answer
Travis JohnstonTravis Johnston
Hi Alain,

Thank you for insight! I should give it another go though with the newer version of SF, I was just following the documentation so didn't think to change the version other than rolling it back. Most of the development is done via Developer Console or within the Apex/VF editor in our staging/dev environments. The only thing that prompted me to look into Force was because I needed to delete some Apex classes from Production in order to remove some packages, and the only way presented was through editing the XML file using Force. I ended up finding a work around which you create the XML file manually and upload a zip file to workbench. This worked pretty well for this small need. 

Though I'm sad to see MavensMate is no longer being supported, I want to keep things in OSX whenever possible and not have to resort to using a virtual machine if I don't have too.