Closed jmuheim closed 10 years ago
Seems like it's fetching the latest 2.3.0
release, because branch is not specified.
But specifying branch is a bad practice: http://stackoverflow.com/a/15786541/532252.
Try asset 'bootstrap-formhelpers', 'git://github.com/someone/some-package.git#<sha>'
unless sha
option is supported for bower-rails
.
Actually, now you can pass SHA as version like:
asset 'bootstrap-formhelpers', '<sha>', github: 'someone/some-package.git'
At the time being, I decided to do as described above:
asset 'bootstrap-formhelpers', # A set of JavaScript to help create user friendly forms
'b69c70158c077449ae2a83f8ac13024944278356',
github: 'jmuheim/BootstrapFormHelpers' # Use this until https://github.com/winmarkltd/BootstrapFormHelpers/pull/219 is merged
Still, I'd rather just use a branch name. I understand that this is risky, but Bundler allows it, too.
I have forked BootstrapFormHelpers and added the
main
directive to it and created a PR.As long as the PR isn't merged, I'd like to use my own branch.
asset 'bootstrap-formhelpers', github: 'jmuheim/BootstrapFormHelpers'
When installing, it seems that bower uses the correct repo:
Sadly, in the
vendor/assets/bower_components/bootstrap-formhelpers/bower.json
file, themain
directive is still missing!But in the used branch it clearly is there, see: https://github.com/jmuheim/BootstrapFormHelpers/blob/master/bower.json
What could have gone wrong here?