Bumped up the version
Ignore Eclipse files.
Add a new requirejs method
I re-factored WebJarAssets such that there are now two Play-independent services. These services should therefore be able to be used in other non-Play scenarios.

The WebJarLocator service is responsible for resolving the location of webjars given a provided class path.

The RequirejsProducer service produces the required require.js bootstrap code that is webjar aware. This service depends on Play's JSON capabilities. However Play's JSON capabilities will be factored out into a standalone library for 2.2: http://mandubian.com/2013/02/21/play-json-stand-alone/.

This service re-factoring also permitted spec2 tests to be written within ease. Tests for the services are also included.

TODO: A test is required to test out the WebJarAssets controller itself.
Added some documentation
having fun migrating to webjars-locator
Formatting
Some tidying up.

TODO: Optimisations
Resolve also from the local maven repo so that we can pick up the latest snapshot for the locator
Now making use of the new WebJarAssetLocator from the webjars-locator project.

The bootstrap JavaScript has also been modified so that partial path based lookups can be supported as per its locate method counterpart.
Changes to accommodate WebJarAssetLocator requiring instantiation.
Fixed a bug with locate where I'd forgotten to strip the requisite prefix.
Removed a comment that is no longer applicable (the todo has been done)
Implemented transitive dependency resolution from a requirejs perspective.

TODO: Get the locator to parse the pom.xml for transitive dependencies.
Added the ability for a webjar's module dependency and other requirejs configuration to be specified in a webjars-requirejs.js file. This file is expected at the root of the META-INF/resources/webjars/{artifactId}/{version} folder. If present then the file is loaded before any other files of this webjar. For example the following contents:

requirejs.config({
  shim: {
    jquery: [ 'webjars!jquery.js' ]
  }
});

Permits an alias to be defined for jquery. If a module requests a dependency on "jquery" e.g.:

define(["jquery"…

then requirejs will be sure to download the webjar for jquery first.

If a module does not use AMD e.g. the bootstrap library, then a configuration can be provided with the webjar for bootstrap like:

requirejs.config({
  shim: {
    'bootstrap': [ 'webjars!jquery.js' ]
  }
});

This will ensure that when bootstrap is loaded from the webjar then jquery will be loaded first.
Externalised the js code so that it can be managed more easily within a JS editor. It can also be linter etc. (and has been!)
Filtered out paths that are not applicable
New unit test for testing out the WebJarAsset controller
Improved efficiency by determining the routes just once
Merge pull request #5 from huntc/master

A webjar-enabled require.js method