These changes were needed by the bug fixes we backported to the 2.0.x
branch. And because we use a no-magic, type safe API, it is safe to do
this kind of small changes. That the benefits of using a statically
compiled language: it is easy to track and fix non compatible change.
> To post to this group, send email to play-framework@googlegroups.com.
> To unsubscribe from this group, send email to
- updated libraries (lessjs and google closure compiler etc.)
-sbt.version=0.11.2
+sbt.version=0.11.3
And
plugins.sbt
-addSbtPlugin("play" % "sbt-plugin" % "2.0.1")
+addSbtPlugin("play" % "sbt-plugin" % "2.0.2")
Niels
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/QKY-EsjIbM8J.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/2r0MABhibzgJ.
Many thanks to all !!!One little gotcha: if I want to use commons-io.FileUtils I must create a lib folder and put the commons-io jar here, if I don't do this, play can't see the jar, very strange...
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/l_DMxje8atwJ.