-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Pushing an artifact on 2.8.3 fails with java.lang.NoSuchMethodError: org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I #745
Comments
I see this too. |
Facing the same problem. I upgraded from 2.8.0 to 2.8.3 to get the newer nrepl versions which seem to be required by Cider. Any help highly appreciated. |
@ska2342 CIDER works fine with Boot 2.8.2, it should inject the correct nREPL version upon |
@alexander-yakushev, I start the REPL via a boot task from the command-line and inject the nREPL from there. Anyhow, I just use 2.8.3 in development and don't commit my local change until this issue is fixed. Thanks for the hint, though. |
@ska2342 In that case, you can also use a Boot task like this to set the nREPL version manually: (deftask cider "" []
(reset! boot.repl/*default-dependencies*
'[[nrepl "0.6.0"]
[cider/cider-nrepl "0.22.0-SNAPSHOT"]
[refactor-nrepl "2.4.0"]])
(reset! boot.repl/*default-middleware*
['cider.nrepl/cider-middleware
'refactor-nrepl.middleware/wrap-refactor])
identity) Then you |
I just upgraded a project from 2.7.2, and I think I ran into this same issue. My stack trace:
I don't think it matters, but just in case: This was on ubuntu 16.04.6, OpenJDK 1.8.0_212, using clojure 1.9.0. |
I'd guess this was caused by upgrading org.apache.maven.wagon/wagon-http: 55e4b55#diff-9db74cbad6290729409297ab0f2a33a6R21 I don't see why Pomegranate wouldn't work with the latest Wagon-http but that does seem like the obvious reason. I think Pomegranate also already has a dependency on wagon-http so maybe boot doesn't even need the direct dependency. |
Is anyone still working on boot? There's no real movement in the project, even with serious bugs like this around. Don't want to be pushy. It's totally fine if the maintainers have more important stuff to work on. I'd just like to know. |
@ska2342 The original authors certainly have no capacity to maintain this project anymore. Unless you are really stuck with Boot (like me), I suggest moving on to either Leiningen or tools.deps. To work around this particular issue, I rolled back to 2.8.2. |
The workaround is fine for me. Been on 2.8.2 for builds and 2.8.3 for local development (nrepl requirement) for ages. I did some heavy investments in my build tooling with boot. Might also consider moving to clojurephant for the more dynamic parts of the build script. Yuck, syntax. ;-) |
But works fine in 2.8.2.
This is the exception trace:
MacOS, JDK 1.8
The text was updated successfully, but these errors were encountered: