net.liftweb.json.XmlExamples failing in Scala 2.12 community build
See original GitHub issueseen at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1080/consoleFull and https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1081/consoleFull
failing commit is 79d036703eedf32a27485574ded1bf2805421ead
last green commit 16f61a0c8d3f647188b0978456e47fc18ecc7293
[lift-json] [info] XML Examples
[lift-json] [info]
[lift-json] [info] + Basic conversion example
[lift-json] [info] + Conversion transformation example 1
[lift-json] [info] + Conversion transformation example 2
[lift-json] [info] + Primitive array example
[lift-json] [info] + Lotto example which flattens number arrays into encoded string arrays
[lift-json] [error] x Band example with namespaces
[lift-json] [error] 'JObject(List(JField(b:band,JObject(List(JField(name,JString(The Fall)), JField(genre,JString(rock)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), JString(My new house)))))))))))))))))'
[lift-json] [error]
[lift-json] [error] is not equal to
[lift-json] [error]
[lift-json] [error] 'JObject(List(JField(b:band,JObject(List(JField(name,JString(The Fall)), JField(genre,JString(rock)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), JString(My new house)))))))))))))))))' (XmlExamples.scala:80)
[lift-json] [error] Actual: ...(rock[)), JField(influence,JString()), JField(playlists,JObject(List(JField(playlist,JArray(List(JObject(List]
[lift-json] [error] [(JField(name,JString(hits)), JField(song,JArray(List(JString(Hit the north), JString(Victoria)))))), JObject(List(JField(name,JString(mid 80s)), JField(song,JArray(List(JString(Eat your self fitter), ]
[lift-json] [error] [JString(My new house)))))))))))))))))]
[lift-json] [error] Expected: ...(rock[]
[lift-json] [error] []
[lift-json] [error] []
[lift-json] [info]
in the community build, I will freeze at 16f61a0c8d3f647188b0978456e47fc18ecc7293 for now
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
2.13: lift-json fails · Issue #887 · scala/community-build - GitHub
I was looking at 2.13 community builds on Jenkins and saw a scala-xml related error for lift-json: [error] ...
Read more >sbt - lift-json with scala 2.10 - Stack Overflow
ResolveException: unresolved dependency: net.liftweb#lift-json;2.5: not found Project loading failed: (r)etry, (q)uit, (l) ...
Read more >lift-json 3.0.1 - framework
net.liftweb. Artifact ID: lift-json_2.12. Version: 3.0.1. Release Date: Dec 13, 2016. Licenses: Apache-2.0. Files: View all. sbt; Mill; Scala CLI; Ammonite ...
Read more >net.liftweb » lift-json_2.12 » 3.3.0 - Maven Repository
Lift Application Development Cookbook (2013) by Gilberto T. Garcia Jr. Lift Cookbook: Recipes from the Community for Building Web Applications with Scala ......
Read more >MappingException when using the Lift JSON Parser giving ...
Im getting a strange exception with the JSON extractor, "net.liftweb.json.MappingException: No usable value for $outer"... has
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 FreeTop 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
Top GitHub Comments
The community build builds everything from source, so only source compatibility matters, not whether the version numbers are the same. I think that before, you declared a dependency on 1.13 (the community build ignores the number) but were using it in a way that was source-compatible with 1.12. There was no issue until you started using 1.13 specific API.
Hmmm… Interesting. Okay, thanks!