-
-
Notifications
You must be signed in to change notification settings - Fork 19
depstar 2.1.297
doesn't seem to pick up jar-name from aliases:
#102
Comments
2.0.211 -> 2.1.279 is a pretty big jump -- can you narrow it down a bit further for me? |
I suspect 2.1.253 will work but 2.1.267 will fail. I think I can see the change that broke things now. |
When I refactored the option processing into the |
Seems to break between 2.0.216 (which works) and 2.1.245 (which doesn't) |
Oh, interesting. So I broke it earlier than I thought, from looking at the git logs... |
Fixed on develop if you want to try via a git dep? |
Tested via git deps, and works. Thanks for the super quick turn around! |
Cool. Will try to get a release cut later today. |
FYI, this will be the last release of |
v2.1.303 has been released to Clojars for you! |
https://github.com/slipset/deps-deploy/blob/master/deps.edn#L29 works as expected with depstar version 2.0.211, ie it produces a jar file named
deps-deploy.jar
When upgrading to depstar version 2.1.297, it produces a directory named
:jar
which containsfile-name
The text was updated successfully, but these errors were encountered: