include more of Lift, not just lift-json

[SethTisue]

see prior discussion with @joescii at scala/scala-xml#150. cc @Shadowfiend

this isn't something I can personally take on; I can sometimes to afford to take on things like lift-json, but 1) since Lift is a whole framework with a big complicated build, and 2) since Lift doesn't typically have open-source downstream dependencies, the cost/benefit isn't there for me.

on the other hand, I'm more than happy to offer as much help and advice as I can if you guys want to take a stab at adding it. and once it gets in, I can generally do light maintenance on it myself and notify you if there are problems.

the documentation at https://github.com/scala/community-builds/wiki is IMO already pretty solid, and I'm very interested in improving it if shortcomings are called to my attention.

[joescii]

I'll get a conversation going in the Lift community regarding this issue. Thanks a million, Seth!

[SethTisue]

Lift was also affected by scala/bug#10437 . this could have been caught by the community build

...but note that (since it only involves Scala and doesn't involve rebuilding other dependencies) could it also have been caught if Lift included the current Scala nightly in their own CI. see https://stackoverflow.com/a/40622879/86485 for info on using the current nightly

[Shadowfiend]

Yes, this is also a good point… We'll mull this over and figure out what the best path forward is.

Are there guidelines as to what kind of stuff should be included in the community build vs not?

[SethTisue]

Are there guidelines

yup, https://github.com/scala/community-builds/wiki/Eligibility

[SethTisue]

closing for inactivity. happy to reopen if someone wants to take it back up. (I don't think it's something I'll tackle myself.)

if Lift wants to include "latest Scala nightly" in their CI matrix, the ticket where we're gathering lore on that is https://github.com/scala/community-builds/issues/599