boot 2019-08-16

@juhoteperi I just made a commit to master that I believe will fix this, not able to test at the moment tho

anyone have a few minutes to build and test master?

@flyboarder Didn' work. But removing wagon-http dependency works.

Pomegranate 1.1.0 uses wagon 3.0.0 so that would be safe version at least

Pomegranate master which has wagon 3.3.2 uses Maven 3.6.0 instead of 3.5.3, so maybe that is required for the new Wagon-http? I couldn't find proper changelogs for the projects so hard to say.

Yes, but that is unreleased

oh really? I thought that version was available already?

Anyway, I think we don't need the direct dependency on wagon-http as it is already dep of pomegranate

agreed, Im not sure why we were explicit in the wagon dependency anyway

Looks like at some point Boot wanted to use more recent version than Pomegranate for some features

so it looks like I cant push to clojars because of jar size limits

we already removed aot to get around this once, but I feel thats a sign of how we are currently building

@flyboarder Have you taken look at this: https://github.com/boot-clj/boot/issues/745 ? Currently pretty much prevents use of 2.8.3 which is also only version which works with recent nRepl