Skip to content

Conversation

raboof
Copy link

@raboof raboof commented Aug 14, 2018

Testing with 2.7.0-M2 now, not thoroughly tested yet though.

Context

Resolve issue #6362

Contributor Checklist

  • Review Contribution Guidelines
  • Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
  • Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
  • Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
  • Provide unit tests (under <subproject>/src/test) to verify logic
  • Update User Guide, DSL Reference, and Javadoc for public-facing changes
  • Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

  • Verify design and implementation
  • Verify test coverage and CI build status
  • Verify documentation
  • Recognize contributor in release notes

@marcphilipp marcphilipp added in:play a:feature A new functionality labels Aug 14, 2018
raboof added a commit to raboof/akka-grpc-play-quickstart-java that referenced this pull request Aug 14, 2018
With akka-grpc from the akka/akka-grpc#302
branch and gradle from the gradle/gradle#6374
branch
raboof added a commit to raboof/akka-grpc-play-quickstart-java that referenced this pull request Aug 14, 2018
With akka-grpc from the akka/akka-grpc#302
branch and gradle from the gradle/gradle#6374
branch
Copy link
Contributor

@marcospereira marcospereira left a comment

Choose a reason for hiding this comment

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

Looking good so far. Need to change tests too.

Copy link
Contributor

Choose a reason for hiding this comment

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

Just add another case without repeting the RoutesCompilerAdapterV24X creatiion:

case PLAY_2_6_X:
case PLAY_2_7_X:
    return new RoutesCompilerAdapterV24X(playVersion, scalaVersion);

Copy link
Contributor

Choose a reason for hiding this comment

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

👍

@marcospereira
Copy link
Contributor

@raboof you can see how tests had changed for Play 2.6 here: #3018.

@raboof
Copy link
Author

raboof commented Aug 20, 2018

I made some updates, but the integration tests fail because they rely on StaticRoutesGenerator which was deprecated in 2.6.0 and now removed in 2.7.0. How should we handle this? Rewrite the tests with InjectedRoutesGenerator, or would that fail with older versions of Play?

@marcospereira
Copy link
Contributor

How should we handle this? Rewrite the tests with InjectedRoutesGenerator, or would that fail with older versions of Play?

Hum... InjectedRoutesGenerator was introduced in Play 2.4 and Gradle supports Play from 2.3 to 2.6 right now. That means you cannot just change to InjectedRoutesGenerator because that will make 2.3 fails (I'm not so sure about how Gradle handles this though).

Is it possible to isolate the tests for 2.7 to force the use of InjectedRoutesGenerator? Or better, make it the default for 2.7 even if it is
configured to do the opposite (and log a warning). Another idea is to remove Play 2.3 support since this version of Play is not maintained anymore and then use InjectedRouterGenerator as you suggested, @raboof.

@blindpirate @marcphilipp WDYT?

@raboof
Copy link
Author

raboof commented Aug 23, 2018

The newest version in the play 2.3 series was released back in 2015... feels like it might be OK to drop support for it? Or do we need to go through a deprecation cycle for that first?

@marcphilipp
Copy link
Contributor

Removal of 2.3 needs a proper deprecation cycle to be removed with Gradle 6.0.

@raboof Could you please post an example of such a problematic test?

Copy link

@octonato octonato left a comment

Choose a reason for hiding this comment

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

Play 2.7.0-RC3 is released, so I updated the references to M2

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"2.7.0-RC3" | "play.core.server.ProdServerStart"
"2.7.0" | "play.core.server.ProdServerStart"

Copy link
Contributor

Choose a reason for hiding this comment

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

Code format got a little weird here.

@raboof raboof mentioned this pull request Feb 2, 2019
Testing with 2.7.0-M2 now, not thoroughly tested yet though.

Signed-off-by: Arnout Engelen <[email protected]>
Signed-off-by: Arnout Engelen <[email protected]>
Unfortunately this will fail because some tests rely on StaticRoutesGenerator
which was deprecated in 2.6.0 and removed in 2.7.0

https://github.com/playframework/playframework/blob/a2186e10178f7084c9493ecc8246b615bf108371/documentation/manual/releases/release27/migration27/Migration27.md#staticroutesgenerator-removed
Signed-off-by: Arnout Engelen <[email protected]>
Signed-off-by: Renato Cavalcanti <[email protected]>
Signed-off-by: Renato Cavalcanti <[email protected]>
@marcospereira
Copy link
Contributor

@marcphilipp @blindpirate,

I think this is now complete and good to review/merge. It is not removing Play 2.3 anymore so that it does not need to go through the deprecation cycle.

WDYT?

@big-guy big-guy added this to the 5.4 RC1 milestone Feb 12, 2019
@big-guy big-guy added the @core Issue owned by GBT Core label Mar 4, 2019
@big-guy big-guy modified the milestones: 5.4 RC1, 6.0, 6.0 RC1 Mar 11, 2019
@adcalder7
Copy link

Please merge.

@octonato
Copy link

@big-guy / @marcphilipp, is there anything missing to get this merged?

@big-guy
Copy link
Member

big-guy commented Mar 25, 2019

@renatocaval We want to get this in, but we're also trying to extract the Play plugin into a separately releasable plugin: https://github.com/gradle/playframework We're not going to get to this PR for the next release (5.4), but I want to circle back on this for the following release.

@dwijnand
Copy link

From #6362 (comment) it seems the new plan is to migrate/port, not merge this PR.

@lacasseio
Copy link
Contributor

We may merge this as-is but the expectation should be to migrate to gradle/playframework. At the moment, this plugin is simply the extraction of the play plugin from the Gradle core to use the current model instead of the software model.

@arjunchhabra
Copy link

@lacasseio - Any update on this item? Whether extracting or merging here, I believe many of us are currently without a path forward.

@lacasseio
Copy link
Contributor

@arjunchhabra Let's migrate the change to gradle/playframework.

For everyone wanting this to be part of the core plugin, let's instead focus on identifying the blocker preventing you from migrating to the gradle/playframework by opening issues over there. We won't be waiting long before the deprecation cycles starts for this core plugin.

@big-guy
Copy link
Member

big-guy commented Sep 17, 2019

I'm going to close this as the playframework plugin has these changes now and should be released shortly.

@big-guy big-guy closed this Sep 17, 2019
@ov7a ov7a removed this from the 6.0 RC1 milestone Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a:feature A new functionality @core Issue owned by GBT Core

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants