It's a bit clunky, but test-specific fixtures can go in src/test/javascript/javascripts/fixtures as described [here](https://github.com/velesin/jasmine-jquery#html-fixtures).
maven-jasmine-plugin appears to serve up static HTML resources too, by default.
Note that the path defined here is the path portion of the URL used to make the HTTP request for the template file.  In other words, the request is made for localhost:port/spec/javascripts/fixtures/template.html, and the jasmine-maven-plugin routes spec/ to src/main/test/javascript.
Reduced nesting for test fixtures, but still is test-specific
Moving the templates to production, where it can now be used as long as the page used in production gets its hands on the <script> tags for the templates.

Right now, the jasmine environment is setting up this dependency by loading the templates from a location relative to the javascript.  It's hard to imagine a production environment doing it quite the same way.
A clunky location for jasmine helpers, but it doesn't appear to be configurable.
Feature-specific template files.
Now the templates live in src/main/webapp, which is a much more production-friendly location (also gets appropriately weaved with javascript in war:war).
src/main/webapp is now configured under jasmine-maven-plugin with a context root of /webapp.