We have just upgraded a large legacy application with which Rajan is intimately familiar to use the asset pipeline.
Here is what the top of the source looks like right now. (Notice that we are getting a full filesystem path for application.js)
Everything after this works correctly and loads all of our individual source files correctly through the asset pipeline, so our tests actually still pass.
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type"/>
<title>Jasmine suite</title>
<link rel="shortcut icon" type="image/png" href="/__JASMINE_ROOT__/images/jasmine_favicon.png">
<link rel="stylesheet" href="/__jasmine__/jasmine.css" type="text/css" media="screen"/>
<script src="/__jasmine__/jasmine.js" type="text/javascript"></script>
<script src="/__jasmine__/jasmine-html.js" type="text/javascript"></script>
<script src="/__jasmine__/json2.js" type="text/javascript"></script>
<script src="/Users/pivotal/workspace/casebook2/app/assets/javascripts/application.js?body=true" type="text/javascript"></script>
<script src="/assets/jquery.js?body=true" type="text/javascript"></script>
<script src="/assets/jquery_ujs.js?body=true" type="text/javascript"></script>
...
Any idea what could be causing this?
Here's our jasmine.yml (with comments stripped)
$ cat spec/javascripts/support/jasmine.yml | egrep -v ^\#
src_files:
- assets/application.js
stylesheets:
- stylesheets/**/*.css
helpers:
- support/helpers/**/*.js
spec_files:
- shared/*.js
- '**/*[sS]pec.js'
src_dir: spec/javascripts/public
spec_dir: spec/javascripts