I want to address <https://github.com/coursier/cou...
# generalh
happy-kitchen-89482
02/05/2018, 3:30 PMI want to address https://github.com/coursier/coursier/issues/754#issuecomment-362950586 so I can switch to using coursier, but I’m unwilling to wade through the excessive functional BS
w
wide-energy-11069
02/05/2018, 5:14 PMI think this depends on https://github.com/coursier/coursier/issues/710
wide-energy-11069
02/05/2018, 5:15 PMwhich @gorgeous-alligator-94763 is working on
g
gorgeous-alligator-94763
02/05/2018, 5:21 PMIs it related? looks like something different to me, but I don’t know coursier as well as you
w
wide-energy-11069
02/05/2018, 5:51 PMoh…not really @gorgeous-alligator-94763 your PR is to fetch a single jar that could exist anywhere, whereas @happy-kitchen-89482 already has a local repo.
If it is a local maven repo already, then https://github.com/coursier/coursier/issues/710#issuecomment-350596224 is already doable, but @happy-kitchen-89482’s issue is to have coursier to understand a local repo but in ivy’s structure
h
happy-kitchen-89482
02/05/2018, 6:58 PMThese aren’t quite the same. The repo I’m talking about might be remote, or local, but the important point is that it doesn’t have ivy.xml files.
happy-kitchen-89482
02/05/2018, 6:59 PMBut it still has ivy URL structure, so we need the ivy placeholder machinery
happy-kitchen-89482
02/05/2018, 6:59 PMwe just need it not to choke if there’s no ivy.xml available
happy-kitchen-89482
02/05/2018, 6:59 PMBut again, could be a remote repo too
w
wide-energy-11069
02/05/2018, 7:06 PMI see. In that case it’s necessary to tell coursier how to behave without ivy.xml. Can you work around it with a dummy ivy.xml?
wide-energy-11069
02/05/2018, 7:18 PMthey have a gitter channel jfyi
h
happy-kitchen-89482
02/09/2018, 2:06 PMIn one case I don't control the remote repo, so I can't stick a dummy file there, but maybe I can work around that
5 Views