New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move bower to ui-classic #14536
Move bower to ui-classic #14536
Conversation
@miq-bot add_label euwe/no, technical debt |
This pull request is not mergeable. Please rebase and repush. |
Assets live there, bower (now) lives there, no point in having the initializer in manageiq proper
manageiq travis should no longer depend on bower & assets, since #13801 and bower configs have moved to ui-classic
The update:bower task is defined in ui-classic. The bin/* change is needed because running rake before bundle install is ..problematic :).
Checked commits https://github.com/himdel/manageiq/compare/488be60745968d7de64b32191901d0c0cf4ce2ff~...d6296e6ed4f560e1a6c56757c6bb3c25129f196b with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@himdel : 👍 🥇 Thanks for this! One more step towards moving to Angular2. Let me buy you a 🍺 on our next team steak session! |
Merge together with ManageIQ/manageiq-ui-classic#823
Right now, bower.json lives in manageiq (except for travis). Mostly because bin/update and bin/setup couldn't handle reading bower.json from manageiq-ui-classic, because ..how do you find where it is :).
This PR removes all traces of bower from manageiq (except for the ignores, because people tend to switch branches :)), moving it to manageiq-ui-classic.
Instead of
bower install -F ...
we now runrake update:bower
, a task which lives in ui-classic.The change to
bin/update
andbin/setup
is needed because running rake tasks is a bit easier afterbundle install
than before :).This also removes caching of
bower_components
from manageiq travis, should not be needed since #13801.@bdunne Can you take a look please? :)