<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 27 Jan 2016, at 00:47, Juraci Paixão Kröhling <<a href="mailto:jpkroehling@redhat.com" class="">jpkroehling@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">If you don't deal with UI stuff, this will not affect you.<br class=""><br class="">It seems that bower > 1.7.2 have moved the bower's executable to another <br class="">location, causing the frontend-maven-plugin to fail at building the UI <br class="">for BTM. Hawkular is *not* affected, as long as it keeps using 1.7.2 (as <br class="">it's the case so far).<br class=""><br class="">So, before updating Bower to a version higher than 1.7.2, make sure that <br class="">the following bug on frontend-maven-plugin is fixed:<br class=""><br class=""><a href="https://github.com/eirslett/frontend-maven-plugin/issues/350" class="">https://github.com/eirslett/frontend-maven-plugin/issues/350</a><br class=""></div></div></blockquote><div><br class=""></div>Juca, </div><div>Thanks for this heads-ups. Very weird since this would seem to break semantic versioning, since that should not be a patch release but a minor version at least.</div><div>But again, that is why we use fixed versions for purposeful upgrades not accidental breakages.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">- Juca.<br class="">_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></div></div></blockquote></div><br class=""></body></html>