-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add some wayt to add additional params to bower #12
Comments
OK, I'll add an option for it. |
I've added two ways to solve this issue (not yet released). 1. bower.dependencies.resolveThis is equivalent to "resolutions" attribute in bower.json. webResource {
bower {
dependencies {
install name: "bootstrap", version: "3.3.6"
install name: "angular", version: "1.5.0"
// Add this to resolve conflict
resolve name: "angular", version: "1.5.0"
} 2. --force-latest optionYou can also resolve conflict by setting "--force-latest" option to "options". webResource {
bower {
// Add this to resolve conflict
options = ["--force-latest"] If you omit these options, the plugin will suggest to add "resolve" option.
|
I've released v1.4.0 that includes two new options above. |
Wow! Thanks. Great! |
Can't use workaround for problem: bower/bower#866
It would be nice to add some way of bypassing some params to bower. like
--force
for example.It's done nice in gradle-appengine-plugin:
Deps:
Reference:
The text was updated successfully, but these errors were encountered: