upjs-rails 0.1.0 → 0.2.0

data/spec_app/spec/javascripts/up/util_spec.js.coffee

@@ -0,0 +1,27 @@
+describe 'up.util', ->
+
+  describe '.isBlank', ->
+
+    it 'returns false for false', ->
+      expect(up.util.isBlank(false)).toBe(false)
+      
+    it 'returns false for true', ->
+      expect(up.util.isBlank(true)).toBe(false)
+
+    it 'returns true for null', ->
+      expect(up.util.isBlank(null)).toBe(true)
+      
+    it 'returns true for undefined', ->
+      expect(up.util.isBlank(undefined)).toBe(true)
+      
+    it 'returns true for an empty String', ->
+      expect(up.util.isBlank('')).toBe(true)
+      
+    it 'returns false for a String with at least one character', ->
+      expect(up.util.isBlank('string')).toBe(false)
+      
+    it 'returns true for an empty array', ->
+      expect(up.util.isBlank([])).toBe(true)
+      
+    it 'returns false for an array with at least one element', ->
+      expect(up.util.isBlank(['element'])).toBe(false)

data/spec_app/vendor/assets/.bowerrc

@@ -0,0 +1,3 @@
+{
+  "directory": "bower_components"
+}

data/spec_app/vendor/assets/bower.json

@@ -0,0 +1,8 @@
+{
+  "name": "dsl-generated dependencies",
+  "dependencies": {
+    "jasmine-jquery": "latest",
+    "jasmine-fixture": "latest",
+    "jasmine-ajax": "latest"
+  }
+}

data/spec_app/vendor/assets/bower_components/jasmine/.bower.json

@@ -0,0 +1,14 @@
+{
+  "name": "jasmine",
+  "homepage": "https://github.com/pivotal/jasmine",
+  "version": "2.0.4",
+  "_release": "2.0.4",
+  "_resolution": {
+    "type": "version",
+    "tag": "v2.0.4",
+    "commit": "d1b4a64a573d69f6cfd07c862a34402efdd0ea06"
+  },
+  "_source": "git://github.com/pivotal/jasmine.git",
+  "_target": "~2.0",
+  "_originalSource": "jasmine"
+}

data/spec_app/vendor/assets/bower_components/jasmine/.gitignore

@@ -0,0 +1,24 @@
+.idea/
+.svn/
+.DS_Store
+site/
+.bundle/
+.pairs
+.rvmrc
+.ruby-gemset
+.ruby-version
+*.gem
+.bundle
+tags
+Gemfile.lock
+pkg/*
+.sass-cache/*
+src/html/.sass-cache/*
+node_modules/
+*.pyc
+sauce_connect.log
+*.swp
+build/
+*.egg-info/
+dist/*.tar.gz
+nbproject/

data/spec_app/vendor/assets/bower_components/jasmine/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "pages"]
+	path = pages
+	url = https://github.com/pivotal/jasmine.git

data/spec_app/vendor/assets/bower_components/jasmine/.jshintrc

@@ -0,0 +1,9 @@
+{
+  "bitwise": true,
+  "curly": true,
+  "immed": true,
+  "newcap": true,
+  "trailing": true,
+  "loopfunc": true,
+  "quotmark": "single"
+}

data/spec_app/vendor/assets/bower_components/jasmine/.npmignore

@@ -0,0 +1,21 @@
+dist/
+grunt/
+node_modules
+release_notes/
+spec/
+src/
+Gemfile
+Gemfile.lock
+Rakefile
+jasmine-core.gemspec
+.rspec
+.travis.yml
+.jshintrc
+.gitignore
+*.sh
+Gruntfile.js
+lib/jasmine-core.rb
+lib/jasmine-core/boot/
+lib/jasmine-core/spec
+lib/jasmine-core/version.rb
+lib/jasmine-core/*.py

data/spec_app/vendor/assets/bower_components/jasmine/.rspec

@@ -0,0 +1 @@
+--color

data/spec_app/vendor/assets/bower_components/jasmine/.travis.yml

@@ -0,0 +1,51 @@
+---
+script: $TEST_COMMAND
+language: ruby
+cache: bundler
+rvm: 1.9.3
+env:
+  global:
+  - USE_SAUCE=true
+  - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
+  - TEST_COMMAND="bash travis-core-script.sh"
+  - JASMINE_BROWSER="firefox"
+  - SAUCE_OS="Linux"
+  - SAUCE_BROWSER_VERSION=''
+  - secure: WSPWhlnC4mWSnSPquX+m1/BCu5ch5NygkaHuM2Nea7lD8oS3XLX8QncZZAsQ4lnNfqoDDuBOizG0AESiqNvE4y6x5qvLLTS6q+ce255ZEMZ71TBdZgDEEvGMEjOPPsVXiXyTQOP1lwOPlrbZvaPgWV7e11KIBab6DfFcQpnvDgo=
+  - secure: SW7CJhZnwaNT749Gdnhvqb5rbXlAOsygUAzh9qhtyvbqXKkmJdBIEsO01YF6pbju1X2twE9JvWCOxeZju43NgQChJlPsGbjY2j3k/TdQeTAJesQe2K7ytwghunI30gjEovtRH0T3w1EmcKPH8yj5eBIcB2OYoJHx8KEC7e68q1g=
+matrix:
+  include:
+  - env:
+    - USE_SAUCE=false
+    - TEST_COMMAND="bash travis-node-script.sh"
+  - env:
+    - JASMINE_BROWSER="safari"
+    - SAUCE_OS="OS X 10.8"
+    - SAUCE_BROWSER_VERSION=6
+  - env:
+    - JASMINE_BROWSER="safari"
+    - SAUCE_OS="OS X 10.6"
+    - SAUCE_BROWSER_VERSION=5
+  - env:
+    - JASMINE_BROWSER="internet explorer"
+    - SAUCE_OS="Windows 8"
+    - SAUCE_BROWSER_VERSION=10
+  - env:
+    - JASMINE_BROWSER="internet explorer"
+    - SAUCE_OS="Windows 7"
+    - SAUCE_BROWSER_VERSION=9
+  - env:
+    - JASMINE_BROWSER="internet explorer"
+    - SAUCE_OS="Windows 7"
+    - SAUCE_BROWSER_VERSION=8
+  - env:
+    - JASMINE_BROWSER="chrome"
+    - SAUCE_OS="Linux"
+    - SAUCE_BROWSER_VERSION=''
+  - env:
+    - JASMINE_BROWSER="phantomjs"
+    - USE_SAUCE=false
+  - env:
+    - USE_SAUCE=false
+    - JASMINE_BROWSER="phantomjs"
+    - TEST_COMMAND="bash travis-docs-script.sh"

data/spec_app/vendor/assets/bower_components/jasmine/CONTRIBUTING.md

@@ -0,0 +1,121 @@
+# Developing for Jasmine Core
+
+We welcome your contributions - Thanks for helping make Jasmine a better project for everyone. Please review the backlog and discussion lists (the main group - [http://groups.google.com/group/jasmine-js](http://groups.google.com/group/jasmine-js) and the developer's list - [http://groups.google.com/group/jasmine-js-dev](http://groups.google.com/group/jasmine-js-dev)) before starting work - what you're looking for may already have been done. If it hasn't, the community can help make your contribution better.
+
+## General Workflow
+
+Please submit pull requests via feature branches using the semi-standard workflow of:
+
+1. Fork it
+1. Clone your fork: (`git clone git@github.com:yourUserName/jasmine.git`)                                                                                                                         
+1. Change directory: (`cd jasmine`)                                                                                                                                                               
+1. Asign original repository to a remote named 'upstream': (`git remote add                                                                                                                       
+upstream https://github.com/pivotal/jasmine.git`)                                                                                                                                                 
+1. Pull in changes not present in your local repository: (`git fetch upstream`)
+1. Create your feature branch (`git checkout -b my-new-feature`)
+1. Commit your changes (`git commit -am 'Add some feature'`)
+1. Push to the branch (`git push origin my-new-feature`)
+1. Create new Pull Request
+
+We favor pull requests with very small, single commits with a single purpose.
+
+## Background
+
+### Directory Structure
+
+* `/src` contains all of the source files
+    * `/src/console` - Node.js-specific files
+    * `/src/core` - generic source files
+    * `/src/html` - browser-specific files
+* `/spec` contains all of the tests
+    * mirrors the source directory
+    * there are some additional files
+* `/dist` contains the standalone distributions as zip files
+* `/lib` contains the generated files for distribution as the Jasmine Rubygem and the Python package
+
+### Self-testing
+
+Note that Jasmine tests itself. The files in `lib` are loaded first, defining the reference `jasmine`. Then the files in `src` are loaded, defining the reference `j$`. So there are two copies of the code loaded under test.
+
+The tests should always use `j$` to refer to the objects and functions that are being tested. But the tests can use functions on `jasmine` as needed. _Be careful how you structure any new test code_. Copy the patterns you see in the existing code - this ensures that the code you're testing is not leaking into the `jasmine` reference and vice-versa.
+
+### `boot.js`
+
+__This is new for Jasmine 2.0.__
+
+This file does all of the setup necessary for Jasmine to work. It loads all of the code, creates an `Env`, attaches the global functions, and builds the reporter. It also sets up the execution of the `Env` - for browsers this is in `window.onload`. While the default in `lib` is appropriate for browsers, projects may wish to customize this file.
+
+For example, for Jasmine development there is a different `dev_boot.js` for Jasmine development that does more work.
+
+### Compatibility
+
+* Browser Minimum
+  * IE8
+  * Firefox 3.x
+  * Chrome ??
+  * Safari 5
+
+## Development
+
+All source code belongs in `src/`. The `core/` directory contains the bulk of Jasmine's functionality. This code should remain browser- and environment-agnostic. If your feature or fix cannot be, as mentioned above, please degrade gracefully. Any code that should only be in a non-browser environment should live in `src/console/`. Any code that depends on a browser (specifically, it expects `window` to be the global or `document` is present) should live in `src/html/`.
+
+### Install Dependencies
+
+Jasmine Core relies on Ruby and Node.js.
+
+To install the Ruby dependencies, you will need Ruby, Rubygems, and Bundler available. Then:
+
+    $ bundle
+
+...will install all of the Ruby dependencies.
+
+To install the Node dependencies, you will need Node.js, Npm, and [Grunt](http://gruntjs.com/), the [grunt-cli](https://github.com/gruntjs/grunt-cli) and ensure that `grunt` is on your path.
+
+    $ npm install --local
+
+...will install all of the node modules locally. If when you run
+
+    $ grunt
+
+...you see that JSHint runs your system is ready.
+
+### How to write new Jasmine code
+
+Or, How to make a successful pull request
+
+* _Do not change the public interface_. Lots of projects depend on Jasmine and if you aren't careful you'll break them
+* _Be environment agnostic_ - server-side developers are just as important as browser developers
+* _Be browser agnostic_ - if you must rely on browser-specific functionality, please write it in a way that degrades gracefully
+* _Write specs_ - Jasmine's a testing framework; don't add functionality without test-driving it
+* _Write code in the style of the rest of the repo_ - Jasmine should look like a cohesive whole
+* _Ensure the *entire* test suite is green_ in all the big browsers, Node, and JSHint - your contribution shouldn't break Jasmine for other users
+
+Follow these tips and your pull request, patch, or suggestion is much more likely to be integrated.
+
+### Running Specs
+
+Jasmine uses the [Jasmine Ruby gem](http://github.com/pivotal/jasmine-gem) to test itself in browser.
+
+    $ rake jasmine
+
+...and then visit `http://localhost:8888` to run specs.
+
+Jasmine uses Node.js with a custom runner to test outside of a browser.
+
+    $ grunt execSpecsInNode
+
+...and then the results will print to the console. All specs run except those that expect a browser (the specs in `spec/html` are ignored).
+
+## Before Committing or Submitting a Pull Request
+
+1. Ensure all specs are green in browser *and* node
+1. Ensure JSHint is green with `grunt jshint`
+1. Build `jasmine.js` with `grunt buildDistribution` and run all specs again - this ensures that your changes self-test well
+
+## Submitting a Pull Request
+1. Revert your changes to `jasmine.js` and `jasmine-html.js`
+  * We do this because `jasmine.js` and `jasmine-html.js` are auto-generated (as you've seen in the previous steps) and accepting multiple pull requests when this auto-generated file changes causes lots of headaches.
+1. When we accept your pull request, we will generate these files as a separate commit and merge the entire branch into master.
+
+Note that we use Travis for Continuous Integration. We only accept green pull requests.
+

data/spec_app/vendor/assets/bower_components/jasmine/GOALS_2.0.md

@@ -0,0 +1,64 @@
+# (Vague) Jasmine 2.0 Goals/(Guidelines)
+
+1. No globals!
+  * jasmine library is entirely inside `jasmine` namespace
+  * globals required for backwards compatibility should be added in `boot.js` (EG, var describe = jasmine.getCurrentEnv().describe lives in boot.js)
+1. Don't use properties as getters. Use methods.
+  * Properties aren't encapsulated -- can be mutated, unsafe.
+1. Reporters get data objects (no methods).
+  * easier to refactor as needed
+1. More unit tests - fewer nasty integration tests
+
+## Remaining non-story-able work:
+* Make a `TODO` list
+
+### Hard
+* Finish killing Globals
+  * Guidelines:
+    * New objects can have constructors on `jasmine`
+    * Top level functions can live on `jasmine`
+    * Top level (i.e., any `jasmine` property) should only be referenced inside the `Env` constructor
+    * should better allow any object to get jasmine code (Node-friendly)
+* review everything in base.js
+* Remove isA functions:
+  * isArray_ - used in matchers and spies
+  * isString_
+  * isDOMNode_
+  * isA_
+  * unimplementedMethod_, used by PrettyPrinter
+* jasmine.util should be util closure inside of env or something
+  * argsToArray is used for Spies and matching (and can be replaced)
+  * inherit is only for PrettyPrinter now
+  * formatException is used only inside Env/spec
+  * htmlEscape is for messages in matchers - should this be HTML at all?
+* Pretty printing
+  * move away from pretty printer and to a JSON.stringify implementation?
+  * jasmineToString vs. custom toString ?
+
+### Easy
+
+* unify params to ctors: options vs. attrs.
+* This will be a lot of the TODOs, but clean up & simplify Env.js (is this a 2.1 task?)
+
+### DONE
+* Matchers improvements
+  * unit testable DONE
+  * better equality (from Underscore) DONE
+  * addCustomMatchers doesn't explode stack DONE
+  * refactor equals function so that it just loops & recurses over a list of fns (custom and built-in) - 2.1? (Tracker story)
+* Spies
+  * break these out into their own tests/file DONE
+
+
+## Other Topics
+
+* Docs
+  * Docco has gone over well. Should we annotate all the sources and then have Pages be more complex, having tutorials and annotated source like Backbone? Are we small enough?
+  * Need examples for:
+     * How to build a Custom Matcher
+     * How to add a custom equality tester
+
+
+
+
+

data/spec_app/vendor/assets/bower_components/jasmine/Gemfile

@@ -0,0 +1,12 @@
+source 'https://rubygems.org'
+gem "jasmine", :git => 'https://github.com/pivotal/jasmine-gem.git'
+# gem "jasmine", path: "/Users/pivotal/workspace/jasmine-gem"
+unless ENV["TRAVIS"]
+  group :debug do
+    gem 'debugger'
+  end
+end
+
+gemspec
+
+gem "anchorman"

data/spec_app/vendor/assets/bower_components/jasmine/Gruntfile.js

@@ -0,0 +1,53 @@
+module.exports = function(grunt) {
+  var pkg = require("./package.json");
+  global.jasmineVersion = pkg.version;
+
+  grunt.initConfig({
+    pkg: pkg,
+    jshint: require('./grunt/config/jshint.js'),
+    concat: require('./grunt/config/concat.js'),
+    compass: require('./grunt/config/compass.js'),
+    compress: require('./grunt/config/compress.js')
+  });
+
+  require('load-grunt-tasks')(grunt);
+
+  grunt.loadTasks('grunt/tasks');
+
+  grunt.registerTask('default', ['jshint:all']);
+
+  var version = require('./grunt/tasks/version.js');
+  var standaloneBuilder = require('./grunt/tasks/build_standalone.js');
+
+  grunt.registerTask('build:copyVersionToGem',
+    "Propagates the version from package.json to version.rb",
+    version.copyToGem);
+
+  grunt.registerTask('buildDistribution',
+    'Builds and lints jasmine.js, jasmine-html.js, jasmine.css',
+    [
+      'compass',
+      'jshint:beforeConcat',
+      'concat',
+      'jshint:afterConcat',
+      'build:copyVersionToGem'
+    ]
+  );
+
+  grunt.registerTask("execSpecsInNode",
+    "Run Jasmine core specs in Node.js",
+    function() {
+      var exitInfo = require("shelljs").exec("node_modules/.bin/jasmine");
+      if (exitInfo.code !== 0) {
+        grunt.fail.fatal("Specs Failed", exitInfo.code);
+      }
+    }
+  );
+
+  grunt.registerTask("execSpecsInNode:performance",
+    "Run Jasmine performance specs in Node.js",
+    function() {
+      require("shelljs").exec("node_modules/.bin/jasmine JASMINE_CONFIG_PATH=spec/support/jasmine-performance.json");
+    }
+  );
+};

data/spec_app/vendor/assets/bower_components/jasmine/MANIFEST.in

@@ -0,0 +1,5 @@
+recursive-include . *.py
+include lib/jasmine-core/*.js
+include lib/jasmine-core/*.css
+include images/*.png
+include package.json

data/spec_app/vendor/assets/bower_components/jasmine/MIT.LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2008-2014 Pivotal Labs
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/spec_app/vendor/assets/bower_components/jasmine/README.md

@@ -0,0 +1,64 @@
+<a name="README">[<img src="https://rawgithub.com/pivotal/jasmine/master/images/jasmine-horizontal.svg" width="400px" />](http://jasmine.github.io)</a> 
+
+[![Build Status](https://travis-ci.org/pivotal/jasmine.png?branch=master)](https://travis-ci.org/pivotal/jasmine) [![Code Climate](https://codeclimate.com/github/pivotal/jasmine.png)](https://codeclimate.com/github/pivotal/jasmine)
+
+=======
+
+**A JavaScript Testing Framework**
+
+Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, [Node.js](http://nodejs.org) projects, or anywhere that JavaScript can run.
+
+Documentation & guides live here: [http://jasmine.github.io](http://jasmine.github.io/)  
+For a quick start guide of Jasmine 2.0, see the beginning of [http://jasmine.github.io/2.0/introduction.html](http://jasmine.github.io/2.0/introduction.html)
+
+Upgrading from Jasmine 1.x? Check out the [2.0 release notes](https://github.com/pivotal/jasmine/blob/v2.0.0/release_notes/20.md) for a list of what's new (including breaking interface changes).
+
+## Contributing
+
+Please read the [contributors' guide](https://github.com/pivotal/jasmine/blob/master/CONTRIBUTING.md)
+
+## Installation
+
+To install Jasmine on your local box:
+
+* Clone Jasmine - `git clone https://github.com/pivotal/jasmine.git`
+* Create a Jasmine directory in your project - `mkdir my-project/jasmine`
+* Move latest dist to your project directory - `mv jasmine/dist/jasmine-standalone-2.0.0.zip my-project/jasmine`
+* Change directory - `cd my-project/jasmine`
+* Unzip the dist - `unzip jasmine-standalone-2.0.0.zip`
+
+Add the following to your HTML file:
+
+    <link rel="shortcut icon" type="image/png" href="jasmine/lib/jasmine-2.0.0/jasmine_favicon.png">
+    <link rel="stylesheet" type="text/css" href="jasmine/lib/jasmine-2.0.0/jasmine.css"> 
+
+    <script type="text/javascript" src="jasmine/lib/jasmine-2.0.0/jasmine.js"></script>
+    <script type="text/javascript" src="jasmine/lib/jasmine-2.0.0/jasmine-html.js"></script>
+    <script type="text/javascript" src="jasmine/lib/jasmine-2.0.0/boot.js"></script>
+
+For the Jasmine Ruby Gem:<br>
+[https://github.com/pivotal/jasmine-gem](https://github.com/pivotal/jasmine-gem)
+
+For the Jasmine Python Egg:<br>
+[https://github.com/pivotal/jasmine-py](https://github.com/pivotal/jasmine-py)
+
+
+
+## Support
+
+* Search past discussions: [http://groups.google.com/group/jasmine-js](http://groups.google.com/group/jasmine-js)
+* Send an email to the list: [jasmine-js@googlegroups.com](mailto:jasmine-js@googlegroups.com)
+* View the project backlog at Pivotal Tracker: [http://www.pivotaltracker.com/projects/10606](http://www.pivotaltracker.com/projects/10606)
+* Follow us on Twitter: [@JasmineBDD](http://twitter.com/JasmineBDD)
+
+## Maintainers
+
+* [Davis W. Frank](mailto:dwfrank@pivotallabs.com), Pivotal Labs
+* [Rajan Agaskar](mailto:rajan@pivotallabs.com), Pivotal Labs
+* [Sheel Choksi](mailto:schoksi@pivotallabs.com), Pivotal Labs
+
+### Maintainers Emeritus
+
+* [Christian Williams](mailto:antixian666@gmail.com), Square
+
+Copyright (c) 2008-2014 Pivotal Labs. This software is licensed under the MIT License.

data/spec_app/vendor/assets/bower_components/jasmine/RELEASE.md

@@ -0,0 +1,63 @@
+# How to work on a Jasmine Release
+
+## Development
+___Jasmine Core Maintainers Only___
+
+Follow the instructions in `CONTRIBUTING.md` during development.
+
+### Git Rules
+
+Please work on feature branches.
+
+Please attempt to keep commits to `master` small, but cohesive. If a feature is contained in a bunch of small commits (e.g., it has several wip commits or small work), please squash them when merging back to `master`.
+
+### Version
+
+We attempt to stick to [Semantic Versioning](http://semver.org/). Most of the time, development should be against a new minor version - fixing bugs and adding new features that are backwards compatible.
+
+The current version lives in the file `/package.json`. This file should be set to the version that is _currently_ under development. That is, if version 1.0.0 is the current release then version should be incremented say, to 1.1.0.
+
+This version is used by both `jasmine.js` and the `jasmine-core` Ruby gem.
+
+Note that Jasmine should *not* use the "patch" version number. Let downstream projects rev their patch versions as needed, keeping their major and minor version numbers in sync with Jasmine core.
+
+## Release
+
+When ready to release - specs are all green and the stories are done:
+
+1. Update the release notes in `release_notes` - use the Anchorman gem to generate the markdown file and edit accordingly
+1. Update the version in `package.json` to a release candidate
+1. Update any links or top-level landing page for the Github Pages
+
+### Build standalone distribution
+
+1. Build the standalone distribution with `grunt buildStandaloneDist`
+1. Make sure you add the new ZIP file to git
+ 1. Should we still do this? Given we want to use guthub releases...
+
+### Release the Python egg
+
+1. `python setup.py register sdist upload` You will need pypi credentials to upload the egg.
+
+### Release the Ruby gem
+
+1. Copy version to the Ruby gem with `grunt build:copyVersionToGem`
+1. __NOTE__: You will likely need to point to a local jasmine gem in order to run tests locally. _Do not_ push this version of the Gemfile.
+1. __NOTE__: You will likely need to push a new jasmine gem with a dependent version right after this release.
+1. Push these changes to GitHub and verify that this SHA is green
+1. `rake release` - tags the repo with the version, builds the `jasmine-core` gem, pushes the gem to Rubygems.org. In order to release you will have to ensure you have rubygems creds locally.
+
+### Release the NPM
+
+1. `npm adduser` to save your credentials locally
+1. `npm publish .` to publish what's in `package.json`
+
+### Finally
+
+1. Visit the [Releases page for Jasmine](https://github.com/pivotal/jasmine/releases), find the tag just pushed.
+ 1. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes.
+ 1. If it is a pre-release, mark it as such.
+ 1. Attach the standalone zipfile
+
+
+There should be a post to Pivotal Labs blog and a tweet to that link.

data/spec_app/vendor/assets/bower_components/jasmine/Rakefile

@@ -0,0 +1,18 @@
+require "bundler"
+Bundler::GemHelper.install_tasks
+require "json"
+require "jasmine"
+unless ENV["JASMINE_BROWSER"] == 'phantomjs'
+  require "jasmine_selenium_runner"
+end
+load "jasmine/tasks/jasmine.rake"
+
+namespace :jasmine do
+  task :set_env do
+    ENV['JASMINE_CONFIG_PATH'] ||= 'spec/support/jasmine.yml'
+  end
+end
+
+task "jasmine:configure" => "jasmine:set_env"
+
+task :default => "jasmine:ci"

data/spec_app/vendor/assets/bower_components/jasmine/grunt/config/compass.js

@@ -0,0 +1,10 @@
+module.exports = {
+  jasmine: {
+    options: {
+      cssDir: 'lib/jasmine-core/',
+      sassDir: 'src/html',
+      outputStyle: 'compact',
+      noLineComments: true,
+    }
+  }
+};