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

Removed Joda functions and dependency from base play-json library. #432

Merged
merged 3 commits into from
May 26, 2020

Conversation

bursauxa
Copy link
Contributor

@bursauxa bursauxa commented Mar 5, 2020

Purpose

// TODO: remove joda after 2.6.0

I think the time has come 🙂

Background Context

play-json-joda has been there for quite some time now, as well as Java 8 Time.

Meanwhile, many projects without use of Joda are still unknowingly downloading Joda through Play-JSON or even more indirectly through Play.

If people maintaining this library are in agreement, I believe we can today move forward with cutting the Joda dependency from the base library, so it stays strictly in play-json-joda.

@bursauxa bursauxa force-pushed the feature/remove-joda branch 2 times, most recently from f5d42d2 to 84e3d04 Compare March 5, 2020 18:15
@bursauxa
Copy link
Contributor Author

bursauxa commented Mar 6, 2020

Note that the build is failing but now that the SBT format is good, I think what's left is a "normal error":

java.lang.RuntimeException: Failed binary compatibility check against com.typesafe.play:play-json_2.12:2.8.1! Found 48 potential problems

It's reporting that I removed methods, which is indeed the intent.

@gmethvin
Copy link
Member

gmethvin commented Apr 9, 2020

You're right, this probably should have been removed in 2.7 or 2.8. We can merge this, but since we're removing methods we might not want to backport it to 2.8. Or maybe since these are deprecated methods we can make an exception. I'm not sure.

@ignasi35
Copy link
Member

ignasi35 commented Apr 9, 2020

Note that the build is failing but now that the SBT format is good, I think what's left is a "normal error":

java.lang.RuntimeException: Failed binary compatibility check against com.typesafe.play:play-json_2.12:2.8.1! Found 48 potential problems

It's reporting that I removed methods, which is indeed the intent.

Yeah, you will have to setup the MiMa exclusions. See the recommended settings that need to be included and test that locally using sbt mimaReportBinaryIssues.

@ignasi35
Copy link
Member

ignasi35 commented Apr 9, 2020

You're right, this probably should have been removed in 2.7 or 2.8. We can merge this, but since we're removing methods we might not want to backport it to 2.8. Or maybe since these are deprecated methods we can make an exception. I'm not sure.

I'd rather not backport.

@bursauxa
Copy link
Contributor Author

bursauxa commented Apr 9, 2020

It's probably safer to keep it for 2.9 indeed, but I am not sure what the schedule for that is... If it is far in the distance, or worse if 2.8 is the last major version for Scala 2, then maybe make an exception.

Copy link
Contributor

@ennru ennru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As these methods have been deprecated since Play JSON 2.6.0 we can finally drop them for 2.9.0.
LGTM.

@ennru ennru force-pushed the feature/remove-joda branch from 84e3d04 to 108774e Compare May 26, 2020 15:37
@mergify mergify bot merged commit 6de5243 into playframework:master May 26, 2020
@ennru
Copy link
Contributor

ennru commented May 26, 2020

Thank you @bursauxa for starting this PR!

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

Successfully merging this pull request may close these issues.

4 participants