[bisq-network/bisq-desktop] Rework recent changes to dependency verification (#1563)

Manfred Karrer notifications at github.com
Fri Jun 8 11:37:22 UTC 2018


I have in my BSQ branch now a similar problem and I think the reason is that the resolving of core is done via jitpack, so we would need to first commit and push the new libdohj version in core. Then once desktop is resolving the dependencies it gets the correct version.

For development I would prefer to have a local resolve. 
Is adding  mavenLocal() to the repo the best approach? If so could we add mavenLocal as preferred resolve strategy?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq-desktop/pull/1563#issuecomment-395734785
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180608/f8337386/attachment.html>


More information about the bisq-github mailing list