Skip to main content

Eclipse and Environment Variables in Mac OS X

After setting the environment variables for a user on a new Mac OS X machine (see post from 12 Oct 2018), I was surprised to see that Eclipse was unaffected by my changes to PATH.
Some details: in my scenario, the development project uses Maven for its builds, but one step runs scripts in a bin folder.

That folder has been added to my PATH. They run fine from the terminal, but from Eclipse the script steps always fail with an error something like "Cannot run xyz - No such file or directory".

The reason turns out to be: the PATH changes are made at the level of my user profile, but the Eclipse app does not refer to my individual user profile (when launched through the Finder or icon tray).

A Google search turns up lots of suggested solutions. There are so many because the approach has changed over the years, and people have different thresholds of what solutions they are willing to use, how much mucking they are comfortable with or allowed to do by their organization.

After researching and experimenting, I recommend modifying the info.plist file in the Eclipse.app. Like all solutions, it has pros and cons.

  • Pro: it works! Eclipse successfully runs the scripts that it had failed to find before the change;
  • Pro: it limits the impact to just Eclipse, no other global impact on other apps or users;
  • Con: you may need to redo the change when Eclipse is upgraded;
  • Con: you cannot use environment variable names for short-hand; you must use the full path.

Here is how to use the Eclipse info.plist file for environment variable changes:

  1. In an editor open the file /Applications/eclipse/Eclipse.app/Contents/info.plist (adjusting for the specific app path for your installation)
  2. Add a new key-dictionary pair to the existing set of key-value pairs. Enter this, again adjusting for your specific installation:
    <key>LSEnvironment</key>
    <dict>
         <key>PATH</key>
       <string>/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:Path_to_My_scripts:Any_Other_Special_App_Paths</string>
    </dict>
  3. Save the file and close
  4. From Terminal run the following command to register this file with Launch Services:
    /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -v -f /Applications/eclipse/Eclipse.app


Popular posts from this blog

Git Reset in Eclipse

Using Git and the Eclipse IDE, you have a series of commits in your branch history, but need to back up to an earlier version. The Git Reset feature is a powerful tool with just a whiff of danger, and is accessible with just a couple clicks in Eclipse. In Eclipse, switch to the History view. In my example it shows a series of 3 changes, 3 separate committed versions of the Person file. After commit 6d5ef3e, the HEAD (shown), Index, and Working Directory all have the same version, Person 3.0.

Scala Collections: A Group of groupBy() Examples

Scala provides a rich Collections API. Let's look at the useful groupBy() function. What does groupBy() do? It takes a collection, assesses each item in that collection against a discriminator function, and returns a Map data structure. Each key in the returned map is a distinct result of the discriminator function, and the key's corresponding value is another collection which contains all elements of the original one that evaluate the same way against the discriminator function. So, for example, here is a collection of Strings: val sports = Seq ("baseball", "ice hockey", "football", "basketball", "110m hurdles", "field hockey") Running it through the Scala interpreter produces this output showing our value's definition: sports: Seq[String] = List(baseball, ice hockey, football, basketball, 110m hurdles, field hockey) We can group those sports names by, say, their first letter. To do so, we need a disc

Java 8: Rewrite For-loops using Stream API

Java 8 Tip: Anytime you write a Java For-loop, ask yourself if you can rewrite it with the Streams API. Now that I have moved to Java 8 in my work and home development, whenever I want to use a For-loop, I write it and then see if I can rewrite it using the Stream API. For example: I have an object called myThing, some Collection-like data structure which contains an arbitrary number of Fields. Something has happened, and I want to set all of the fields to some common state, in my case "Hidden"

How to do Git Rebase in Eclipse

This is an abbreviated version of a fuller post about Git Rebase in Eclipse. See the longer one here : One side-effect of merging Git branches is that it leaves a Merge commit. This can create a history view something like: The clutter of parallel lines shows the life spans of those local branches, and extra commits (nine in the above screen-shot, marked by the green arrows icon). Check out this extreme-case history:  http://agentdero.cachefly.net/unethicalblogger.com/images/branch_madness.jpeg Merge Commits show all the gory details of how the code base evolved. For some teams, that’s what they want or need, all the time. Others may find it unnecessarily long and cluttered. They prefer the history to tell the bigger story, and not dwell on tiny details like every trivial Merge-commit. Git Rebase offers us 2 benefits over Git Merge: First, Rebase allows us to clean up a set of local commits before pushing them to the shared, central repository. For this

Code Coverage in C#.NET Unit Tests - Setting up OpenCover

The purpose of this post is to be a brain-dump for how we set up and used OpenCover and ReportGenerator command-line tools for code coverage analysis and reporting in our projects. The documentation made some assumptions that took some digging to fully understand, so to save my (and maybe others') time and effort in the future, here are my notes. Our project, which I will call CEP for short, includes a handful of sub-projects within the same solution. They are a mix of Web APIs, ASP MVC applications and Class libraries. For Unit Tests, we chose to write them using the MSTest framework, along with the Moq mocking framework. As the various sub-projects evolved, we needed to know more about the coverage of our automated tests. What classes, methods and instructions had tests exercising them, and what ones did not? Code Coverage tools are conveniently built-in for Visual Studio 2017 Enterprise Edition, but not for our Professional Edition installations. Much less for any Commun