On 4 Dec 2014, at 18:35, John Sanda <jsanda@redhat.com> wrote:

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?

It’s subjective. Its a UI just for rhq-metrics so my tendency is that it probably should be in rhq-metrics. But, if we want to split the project into other pieces, it might make sense. Same question could be asked of clients(i.e., ptrans). Its not part of core but associated with the project and their could be many different adapters. The UI is not part of core but is associated only with this project. If we look at other projects, it is not normal that UIs are their own project so my guess is no.  Just depends at what granularity  we want for the repos. BTW, the charting package has just been split to its own repo because it could be used across many other projects (and bower packages require their own repo).


_______________________________________________
rhq-devel mailing list
rhq-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel