Checking project for null to fix the unit test build.
TISTUD-6016 Android : Default emulator is not auto created on windows
TISTUD-5901 Turn off code coverage on unit test build for studio3-core-development
  - Only run the coverage tasks if "instrument.code" property exists
TISTUD-5904 Turn on FindBugs analysis for nightly build of studio3
  - First try at adding findbugs target to build
Fix up the findbugs result dir
try to fix up the path to the jar files to analyze for Findbugs
Try to separate out testing from building test fragments so that nightly can run tests and findbugs without needing to rebuild.
Fix path to findbugs ant jar
TISTUD-5904 Turn on FindBugs analysis for nightly build of studio3
- Try to filter what we run Findbugs on to only our own code
TISTUD-5939 Update studio3-core-development-tests to run using eclipse test framework 4.3.1 and JUnit 4
  - Upgrade to testing framework 4.3.1
get the library file path right, dummy
- Exclude assignment of plugin singleton in start/stop from FindBugs
- try to exclude code in com.aptana.jetty.util.*
TISTUD-5941 Move from Emma to JaCoCo for code coverage
Oops, need to call -post-test after running tests!
fix compile error
-  Allow for an empty password for sudo (which is the case on our build machine)
- When using empty sudo password, don't pass along -S switch and don't pass any password on STDIN
- Have SudoManager also handle empty passwords, and try to properly verify them
- add method to get listing of versions available for an NPM package