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

[WIP] Upgrade/play 2.6.0 m #133

Merged
merged 15 commits into from Jun 24, 2017
Merged

[WIP] Upgrade/play 2.6.0 m #133

merged 15 commits into from Jun 24, 2017

Conversation

lloydmeta
Copy link
Owner

@lloydmeta lloydmeta commented Apr 5, 2017

Waiting on:

  • Play 2.6.0 official release
    • Remove suffix

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 01f56e5 on upgrade/play-2.6.0-M into 335bce5 on master.

@lloydmeta lloydmeta mentioned this pull request Apr 5, 2017
5 tasks
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f317076 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f317076 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 1ac9028 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 1ac9028 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling eedbdb2 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 4bd9598 on upgrade/play-2.6.0-M into 335bce5 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 18c4e04 on upgrade/play-2.6.0-M into 469c48e on master.

@ShaneDelmore
Copy link

I have been using this branch with no problems, thank you for publishing it. If you update it to Play 2.6-m7 would you consider publishing this as a -M branch instead of -SNAPSHOT? It's a small difference but being a snapshot invalidates all sbt caching when using it as it is always checking if a newer snapshot has been published which I would not expect being based on a milestone release.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2ee0c5c on upgrade/play-2.6.0-M into 469c48e on master.

@lloydmeta
Copy link
Owner Author

lloydmeta commented May 17, 2017

@ShaneDelmore good point; done. I just published new versions of the 2.6.0 integrations:

  • enumeratum-play (based on M5, which is the latest according to the official site)
  • enumeratum-play-json (based on M7)

both suffixed with 2.6.0-Mx

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 90b3ed9 on upgrade/play-2.6.0-M into ae87d9d on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 90b3ed9 on upgrade/play-2.6.0-M into ae87d9d on master.

@lloydmeta lloydmeta merged commit 608c62b into master Jun 24, 2017
@lloydmeta lloydmeta deleted the upgrade/play-2.6.0-M branch June 24, 2017 14:54
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.

None yet

3 participants