-
Notifications
You must be signed in to change notification settings - Fork 9
GradleTest
fails alleging an issue with jackson-bom
version 2.15.0-rc1
#18
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
Comments
@jjohannes I was wondering if you had an idea of what is the problem here? |
@cowtowncoder happy to check. The issue is valid. Which shows, at least, that this test is useful to some degree. Maybe we could print a more actionable message though. Two things to check in such a case:
I am pretty sure it is the same problem as with We can do the same fix in the |
Ah! Yes, that makes sense. Should have remembered... I'll have a look at this tomorrow, hope we can get it fixed for 2.15.0-rc2. And yes, improved message would always be a nice improvement. Although at least now I have better idea what to look for (which is pretty obvious in hindsight -- I should have been able to figure it out). |
Fixed via FasterXML/jackson-core#966 I hope. |
2.15.0-rc2 was released, no longer failing, closing. |
With Jackson 2.15.1 release (https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.15.1), getting closer to getting
|
Good to hear that the issue with Regarding mrbean: was this just some timing issue with the releases and this will be fine in 2.16? Or is it unclear why this problem still exists? |
@jjohannes I think it's a real problem, need to fix project definition in pom.xml similar to how Afterburner was changed. I forget what specifically is involved; or why it wasn't included as a failure earlier. |
So, after publishing
2.15.0-rc1
,GradleTest
started failing with:At first I was wondering if that might be due to:
FasterXML/jackson-core#955
but after upgrading (just to be sure), via #17 failure persists. Perhaps that's just due to oddities of handling of (Pre-)Release Candidates, version number. Or maybe I made some mistake in publishing. But would be good to figure out.
The text was updated successfully, but these errors were encountered: