On Dec 4, 2014, at 8:46 PM, mike thompson <mithomps@redhat.com> wrote:

Here is the second video in the three part series about Bower package management.

This video focuses on package conflict resolution in bower:


The next and last in the series(although there will probably some tips/tricks videos), is a video on publishing and registering your own bower packages(hint: its easier than maven).

IMO, bower is nice, lightweight, focused solution to front-end asset management involving javascript, css, images and other UI assets(not just Angular). It allows easy versioning, deployment and transitive dependency management for JS UIs.

I have not watched the videos yet, but I do have one question. Since we we have separate build tools for UI assets, would it be better/easier to put the those UI pieces in their own separate project instead of wrapping them with the maven build as we currently do?