title: AngularJS and Playframework integration
body: <p>I'm trying to figure what is the best way of integrating my AngularJS and Play framework projects in order to package them together as front-end and back-end respectively.</p>
  
  <p>I have found this <a href="http://basav.github.com/blog/Angular-JS-Phonecat-example-with-Play-Framework/" rel="nofollow">blog post</a> talking about the exactly same problem but mine is slightly different because I'm using Play framework 1.2.5 instead of 2.0, thus I can't control the assets folder with:</p>
  
  <blockquote>
    <p><code>GET     /assets/*file               controllers.Assets.at(path="/public", file)</code></p>
  </blockquote>
  
  <p>There is no evident/effective difference because the guy is exposing a lot of files that don't really are part of his application, the files under /public different of javascripts/, images/ and stylesheets/. That is what I would like to avoid, exposing such files in production or having to remove them before deploy to production.</p>
  
  <p>It's worth mentioning that the files under /public different of javascripts/, images/ and stylesheets/ are AngularJS files/folders and mostly related to testing. AngularJS uses Jasmine internally to test (that is what I have read), so the files are Jasmine files disguised of AngularJS files.</p>