...
The following message will display in the development console in IntelliJ if playframework is unable to locate JNotify is the in this case:
Cannot load the JNotify native library (no jnotify_64bit in java.library.path)
Play will check file changes for each request, so expect degraded reloading performace....
Create a new folder called "jnotify" in the "toolslib" directory: e.g. path/to /Library/Java/JavaVirtualMachines/jdk1.8/tools.0_77.jdk/Contents/Home/lib/jnotify
Next, paste jnotify-0.94.jar, libjnotify.so, and libjnotify.jnilib to the path/to/jdk1.8/toolslib/jnotify folder.
Finally, add this folder to your the following argument (adjusted with your correct path) to the JVM arguments in your Run Configuration for Clowder in IntelliJ:
-Djava.library.path=...
/Library/Java/JavaVirtualMachines/jdk1.8.0_77.jdk/Contents/Home/lib/jnotify
Builds too slow? Increase -Xmx
In IntelliJ, often the default memory constraints are too low for Scala projects.
From the top menu, choose Help → Edit Custom VM Options and find the -Xmx flag.
This is your JVM's maximum memory heap size, which defaulted to 750MB for me.
Upping this value will decrease the amount of garbage collection necessary during build, and can therefore increase your overall build speed/tools/jnotify in IntelliJ.
Required Dependencies
There are still a few things missing before Clowder will run properly
...