[2.4.3 Java] Upgrade to 2.4.6 is more involved than I thought?

[Slim Slam]

I was expecting that upgrading from Play 2.4.3 to 2.4.6 would be a fairly

minor affair, but it seems that I haven't been paying attention for a while (?)

We're using Java 8.

Our Play 2.4.3 app generates no warnings or errors and runs fine. 

Downloading the latest 2.4.6 package and creating a new Play java app, it seems

that these are the upgrade steps:

build.sbt

scalaVersion := "2.11.6"
 goes to
scalaVersion := "2.11.7"

Plugins.sbt

addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.4.6")
 goes to
addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.5.3")

activator-launch-1.3.10.jar
replaces
activator-launch-1.3.7.jar

After doing these three steps and recompiling, I see these warnings

[warn] There may be incompatibilities among your library dependencies.
[warn] Here are some of the libraries that were evicted:
[warn] * com.typesafe.play:play-java-ws_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-jdbc-evolutions_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-cache_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-java-jdbc_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-netty-server_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-java_2.11:2.4.0 -> 2.5.3
[warn] * com.typesafe.play:play-server_2.11:2.4.0 -> 2.5.3

And every single line of our routes file generates an error of the form:

[error] routes:LINENUMBER: value SOMEVALUE is not a member of controllers.SOMECONTROLLER FILE

I'm not sure where the changes are between Play 2.4.3 and 2.4.6 that we missed. Can someone please fill me in?

Thanks!

[Marcos Pereira]

I highly recommend that you read the migration guide:

https://playframework.com/documentation/2.5.x/Migration25

This section explains the problem you are having with the routes:

https://playframework.com/documentation/2.5.x/Migration25#Routes-generated-with-InjectedRoutesGenerator

About the dependencies eviction, it could be that:

1. You are using some other dependency that is adding Play 2.4.6 transitively

2. You are manually declaring play dependencies.

Either way, we need to see  your build.sbt file to help you to figure out what is happening.

Best,

--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to play-framewor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/3b057050-48ad-4d6d-8a0d-2f7e994438e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Slim Slam]

So what you're saying is that there's a bug in the 2.4.6 release of Play because it's

creating new applications that are targeted at Play 2.5.3 instead of Play 2.4.6 ?

I'm upgrading to Play 2.4.6, not Play 2.5.x\

J

[Greg Methvin]

Hi Slim,

Upgrading to 2.4.6 should be as simple as changing the version to 2.4.6 in plugins.sbt. If you are changing the version to 2.5.3 then you are in fact upgrading to 2.5.3.

Greg

To view this discussion on the web visit https://groups.google.com/d/msgid/play-framework/b84d34be-58a2-4773-984c-cc6433ba4527%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Greg Methvin

Senior Software Engineer

Lightbend, Inc.