title: Are there best practices in using bower in a source-controlled, mavenized, java web application
body: <p>I'm quite new to bower but not web application development.  Previously, I've just downloaded the required JavaScript and CSS files from third-party libraries/frameworks and placed them into my web application's src/main/webapp/scripts (or equivalent) folder.  This ensures that only the files needed by the web application are deployed.</p>
  
  <p>With my default setup, the entire bower_components directory will be committed to source control and if I follow the examples for referencing a bower package, e.g.,</p>
  
  <pre><code>&lt;script src="/bower_components/jquery/jquery.js"&gt;&lt;/script&gt;
  </code></pre>
  
  <p>I'm going to end up deploying the entire bower_components directory with my web application.  This seems like huge overkill (especially were I to use jQuery UI because all the themes are downloaded into bower).</p>
  
  <p>Is there a best practices in using bower with a web application such that the application isn't bloated with unnecessary third-party library files?  Please remember that this is also Java and Maven web application.</p>