… exceptions running on Ruby 2.
…r can do to improve this and it should be handled by the build tools anyhow.
…g which file has a lot of wasted space and the current way to improve efficiency. Ideally, Chance would use the wasted space itself, but that is a difficult problem to solve.
…uild path message to info level.
…the build process.
…result in not being able to kill sc-server.
… matched .git directories as an ignored path. This prevents excessive CPU usage when dealing with submodules and frameworks checked out within a project.
…ten gem. This prevents the case where quick subsequent file system changes are assumed to invoke multiple overlapping scans of the project directory, which caused the Ruby process to consume ~100% CPU.
This just looks for phantomjs/test_runner.js in the /sproutcore target, then invokes it under PhantomJS. PhantomJS is assumed to be in the PATH. All arguments are simply passed through to PhantomJS. The ability to pass through arguments like this was not present in thor 0.14, so I bumped the version requirement as well.
While fixing the previous issue, I noticed that the help string for whitelist/blacklist/accept mentions a default value, but there was no default value set for these options.
The addition of the PhantomJS test runner exposed the fact that there isn't a good way to exclude parts of a target from being included in a build. So I added a new :exclude option that can be used to tell Abbot to exclude directories from a build.