Added null check in the instrumentation JavaScript to prevent resetting coverage metrics each time the file is loaded. This was an issue for a project that uses Require.js contexts to isolate the modules for each Jasmine spec, which allows each spec to replace modules with stubs or mocks without impacting the other specs.
Merge pull request #112 from gzimmer/master

Changes to prevent coverage metrics from being reset each time an instrumented file is loaded.
Fixing HTMLUnit ignores noInstrumentPatterns

Instrumenting using the phantomJS driver ignores noInstrumentPatterns.
Reverting GitIgnore
Merge pull request #116 from worldjoe/master

Fixing HTMLUnit ignores noInstrumentPatterns
Simplest way to work around the timeout problem
Replace override of window.setTimeout, etc. with Jasmine-specific monitoring for completion, making it easy in theory to support other testing frameworks.
Replace override of window.setTimeout, etc. with Jasmine-specific monitoring for completion, making it easy in theory to support other testing frameworks (reverted diff due to IntelliJ reformat).
Merge pull request #119 from johnomalley/master

Overriding the timer doesn't really work... created Jasmine-specific monitoring for completion
[maven-release-plugin] prepare release saga-root-1.5.3
[maven-release-plugin] prepare for next development iteration
releasing Gradle plugin version 1.5.3
preparing for next development iteration 1.5.4-SNAPSHOT
updated version
Update README.md