Skip to content
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

Not compatible with Scala 2.12.+ #23

Open
skoky opened this issue Apr 16, 2017 · 7 comments
Open

Not compatible with Scala 2.12.+ #23

skoky opened this issue Apr 16, 2017 · 7 comments

Comments

@skoky
Copy link

skoky commented Apr 16, 2017

Please make it compatible with Scala 2.12.+. Once linked in a project using this scala version I get this error:

unresolved dependency: com.mediamath#scala-json_2.12;1.0: not found

unresolved dependency: com.mediamath#scala-json_sjs0.6_2.12;1.0: not found

@colinrgodsey
Copy link
Contributor

Yea, still working on the 2.12 release. There's some new oddities in the macros we're trying to figure out. Guessing we should have it within a week

@apple-corps
Copy link

doh!

@colinrgodsey
Copy link
Contributor

colinrgodsey commented Apr 27, 2017

Still no real resolution on the custom annotation macro issues yet, hoping to have something soon.

Everything should be available on this branch if you wanted to do a local build: https://github.com/MediaMath/scala-json/tree/2.12.x

Should be able to publishLocal from SBT there:

> ++2.12.1
> jsonJVM/publishLocal

Really the only feature not working so far is the ability to use "custom annotations", which is a rather tertiary feature

@skoky
Copy link
Author

skoky commented Apr 28, 2017

Yes, it works. I had to run this as well

jsonJS/publishLocal

@colinrgodsey
Copy link
Contributor

👍

@skoky
Copy link
Author

skoky commented Oct 21, 2017

Any progress on this or is the lib dead?

@colinrgodsey
Copy link
Contributor

not dead, still actually being used rather readily. unfortunately it has gone rather stale this year, but there are features coming up (JSON schema) and 2.12.x. The 2.12 stuff got pushed back because we held back up our upgrades inhouse here, but should be fixed by the end of the year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants