-
Notifications
You must be signed in to change notification settings - Fork 41
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
Support for Play 2.7 #92
Comments
The currently supported Play versions are documented in the user guide. Play 2.7 is not supported yet. I am hoping that we can add support for newer Play versions as soon as we have more adopters for this plugin. |
To be sure, there's no way to build Play 2.7 on gradle right now, right? I tried the legacy plugin which fails with the same error |
That's correct. The old and the new plugin have almost identical feature sets at the moment. The main difference is:
Additionally, you might want to check out this migration portion of the guide. |
Any news on this issue? ( 2.8.0 is already around the corner https://github.com/playframework/playframework/releases/tag/2.8.0-M3 ) Thank you. |
@big-guy Can you comment on the plans for this? |
@wooyea does it also work with 2.8.0 ? |
Probably not. Supported version prefix was hardcoded. |
@wooyea thanks for the info. It's a pity since Play 2.8 has just been released :( . |
Do you have any forecast for release date? |
I think it's the other way around: you'll get more adopters as soon as the plugin supports the newest play versions. (I typically would like to test it with the newest play version before even thinking of using it anywhere.) Vicious circle, this? |
Here I even considered downgrading Play to use this plugin |
Hi,
I just need the current version to be released. I couldn't be locked in
2.6. So if you have a target date I could evaluate if not I've to find
alternatives.
Arnaud Pflieger <[email protected]> escreveu no dia quarta,
5/02/2020 à(s) 07:51:
… Here I even considered downgrading Play to use this plugin
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#92?email_source=notifications&email_token=AEKGD4UB5PKME3XX3WRQUILRBJ4XTA5CNFSM4HFRPH5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK2T5GY#issuecomment-582303387>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEKGD4X22TCKFQ6C2B2C7DTRBJ4XTANCNFSM4HFRPH5A>
.
|
Given that's been more than a year since Play 2.7.0 was first released, and now there's even 2.8 available, would it be possible to update the plugin to support 2.7? |
No one will adopters this since doesn't support 2.8. who will start using this with play 2.5, or even 2.6 not fully supported? |
I sent a PR for Play 2.8 support: #133 |
I have spent the majority of the last 3 hours trying to keep Gradle, how is this still not solved? We need:
|
same here. @bmuschko / @big-guy any idea if support for 2.7 will ever land? At some point, we devs would like to have a definitive [yes, no] answer so that we can proper decisions on the projects we will start |
I'm happy to merge changes once #136 is resolved. Currently, I can't really trust the CI to verify if a change will break anything. Once I have confidence in CI, I'll be more confident merging external PRs. |
@polentino Unfortunately, I am not involved in the project anymore. Cheers! |
This has been resolved in v0.10 |
Using
I get
Not a supported Play version: 2.7.0. This plugin is compatible with: [PLAY_2_3_X, PLAY_2_4_X, PLAY_2_5_X, PLAY_2_6_X].
:)
The text was updated successfully, but these errors were encountered: