Fix relative URLs in bower components

[jimpo]

There are many bower components with CSS files that have relative image URLs in them. For example, Bootstrap 2, jQuery UI, and JCrop all do this. This is fine in development, but when the assets are compiled with rake assets:precompile, the links to these images break. This is why Rails has special helpers for asset links.

I have created a bower:resolve task to replace all relative paths to an asset_path call. This way all CSS files in bower components will work in both development and production.

[coveralls]

Coverage remained the same when pulling 857a345 on jimpo:master into 520884a on 42dev:master.

[coveralls]

Coverage remained the same when pulling e5c4943 on jimpo:master into 520884a on 42dev:master.

[SergeyKishenin]

Thanks for the request. This will affect *.css files that are already installed, right? What about the newly installed assets? rake bower:resolve should be run every time anybody add a new package? Maybe it would be better to make it "just work"?

[jimpo]

Since bower components will work in development regardless, it only has to be run before precompilation. That is why I added the prerequisite tasks to assets:precompile. However, it wouldn't hurt to just run the resolve_asset_paths method in the install and update tasks.

[SergeyKishenin]

Agree, merged!

[rharriso]

Thanks for the new feature.

Could you add an explanation to the README?

[jimpo]

#51

[SergeyKishenin]

e5c4943 forces to have Bower installed on a remote server. Is it a good idea? Sometimes it can be excess for someone.

Maybe should we provide an option to choose how to deal with assets?