Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
NPE during dependency resolution
See original GitHub issueRunning update on the minimized reproducer project at github.com/hseeberger/test fails resolution with NullPointerExceptions.
Tried with Java 8 and 9, using sbt 1.1.1.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
NPE on dependency resolution when given an invalid ...
I stumbled over a NPE today, after changing the dependencies of my project. I have a list of all external jars on which...
Read more >[#MNG-5307] NPE during resolution of dependencies - Apache
When building a project for the first time, maven fails with an internal NPE (see stacktrace below). This happens in case the first...
Read more >Re: [tycho-user] NPE during dependency resolution of platform ...
I'm pretty sure I've isolated this issue to Tycho 0.20.0. For our > > projects with native code, we have the main host...
Read more >356 (JNA maven dependency resolution causes NPE)
Something in commit 0030b89b2eb24b0b63b5f1ca4d4c9a7644eea02d broke the JNA maven dependency resolution: (sly@cyruss-mbp):~/src/abcl$ ./abcl
Read more >[jira] Created: (MNG-4785) NPE in dependency resolution code for ...
NPE in dependency resolution code for TC plugin ... Terracotta Maven plugin 1.4.0 test produces NPE in 3.0-beta-3, but works fine in 3.0-beta-2...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
According to https://github.com/sbt/librarymanagement/issues/180 is related to missing content-types when delivering artifacts from repositories. I discovered that in @hseeberger’s case it was repo.akka.io which didn’t provide any content-type for pom files. I fixed that on our server and now the reproducer works (see also https://github.com/akka/akka/issues/24536).
Still the original problem should be solved not to throw NPEs in any case.
Fixed in https://github.com/sbt/librarymanagement/pull/214