migration to play 2.5

[mazorigal]

Hi,

we migrated to play2.5 from 2.4
and now I am getting:
Error injecting constructor, java.lang.NoClassDefFoundError: Could not initialize class com.eclipsesource.schema.package$

and also that one:
caused by: java.lang.NoSuchMethodError: play.api.libs.functional.syntax.package$.functionalCanBuildApplicative(Lplay/api/libs/functional/Applicative;)Lplay/api/libs/functional/FunctionalCanBuild;
at com.eclipsesource.schema.internal.serialization.JSONSchemaReads$class.tupleReader(JSONSchemaReads.scala:185)
at com.eclipsesource.schema.package$.tupleReader$lzycompute(package.scala:12)
at com.eclipsesource.schema.package$.tupleReader(package.scala:12)
at com.eclipsesource.schema.internal.serialization.JSONSchemaReads$class.$init$(JSONSchemaReads.scala:23)
at com.eclipsesource.schema.package$.(package.scala:13)
at com.eclipsesource.schema.package$.(package.scala)

is there any issues with the play-json-schema-validator and play2.5 ?
(I see that you are using addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.3.3") while in scala migration to 2.5 stays
addSbtPlugin("com.typesafe.play" % "sbt-plugin" % "2.5.x"))

Thanks,

[edgarmueller]

Hi, what version of the validator are you using? Since 0.7.0 the validator has been updated to Play 2.5.0 and the web frontend is also built with Play 2.5.0 (but you are probably right that I should update plugins.sbt). Did you also try to do a clean; compile with sbt?

[mazorigal]

indeed my fault.

I forgot to update the validator version in my project.

looks like all fine now.

Thanks,

[edgarmueller]

Glad you got it working. If there's anything else, let me know.