-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Dependency is not upgraded if appears more than once in deps file #50
Comments
@dharrigan Hmm.. It seems to work well in my environment.
|
That's interesting. I'm able to reproduce it 100% I discovered that if I put another entry before the i.e., with this
Then it upgrades successfully, but with this deps.edn, it does not...
So it appears that having an entry prior to the duplicate jar deps entry, causes the second one not to upgrade. |
That's weird... It work for me.
Ah... if one of the same entries has the latest version, the version check may not work properly, so maybe this is the cause?
|
Ah, that sounds like you've found the problem! :) |
I'll fix it. thanks! |
@dharrigan I tried to fix in |
Hi! Confirm fixed :-) Arigato! |
@dharrigan Thanks for your confirmation! |
If one has a
deps.edn
file like this:On running
clj -M:antq
with this alias:Only the first dependency is upgraded, with the second one being ignored. If
uberjar
is commented out, then the second one is upgraded (and vice versa).The text was updated successfully, but these errors were encountered: