How to fix error :xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun after update to MacOS Mojave ?

Solution for

• Git
• macOS Mojave 10.14.x

STORY:
Did you upgrade your amazing macOS Mojave? Did you wish to crack on your project and start to use git but you were hit with error: 

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

SOLUTION:
You need to install Command Line Developer Tools, so simply run this command:

xcode-select --install

How to set groovysdk on mac in IntelliJ IDEA

The solution works for:
Groovy 2.4.12
IntelliJ IDEA 2017.2.6
macOS 10.12.6
Homebrew 1.5.10
It should work with other versions too.


STORY:
    I tried to Config groovy SDK to use in IntelliJ IDEA ... but you need specific path which is .. something like that: /usr/local/Cellar/groovy/x.y.z/ libexec but I couldn't see usr folder. 
As it turns out you need to use a magical shortcut to enable a view of hidden files/folder in Finder on Mac.
How?

SOLUTION:

1. Go to Project Structure
2. Go to Global Libraries
3. Press +
4. Select Java 
5. In Finder, press  ⌘⇧. ( Command key, SHIFT key  dot key a the same time ) to enable 'view hidden files' mode
6. Go to top level (MachintoshHD)
7. go to /usr/local/Cellar/groovy/x.y.z/libexec and press open if you don't see usr folder... perform step 5 (and ensure you have all privileges required) 
8. Press create
9. Done :)

How to find Gradle home path inc on Mac if you install it using homebrew ?

It works on:

• MacOS Siera 10.12.6
• IntelliJ IDEA 2017.2.5
• Gradle 4.3

    It turns out in my new work I will enjoy my development on macOS that is loved by hipster developers. As expected I needed to adjust mindset to macOS universe as I used to develop on Windows.

After you installed Gradle using homebrew,
Go to project in IntelliJ IDEA:
In Gradle SDK you simply type:

    /usr/local/Cellar/gradle/4.3/libexec


and it works... sort of.

Obviously replace 4.3  with version you are using.