* Yobi users who upgraded to Play 2.3.x will have a problem when running the Yobi with a bug
which is originated from H2 1.3.175v (https://code.google.com/p/h2database/issues/detail?id=543)
* Added H2's the latest version 1.4.184 to build.sbt,
and It works well without editing PlayFramework modules's dependency files.
* As the latest version of H2 suggests, you may have to update application.conf's 'db.default.url' value
to not to use implicit relative path.
* If you use implicit relative path, then you have to change it to use explicite relative path like this:
jdbc:h2:file:yobi;MODE=PostgreSQL -> jdbc:h2:file:~/yobi;MODE=PostgreSQL
CallAction should be called after the app starts.
This test seems to be broken since we start to use play-2.3. I wonder
why this test passed when we used play-2.1.
* ArrayIndexOutOfBoundsException can be occurred if a user's notifications are smaller then
the size of notifications to get.
* This prevents the exception and the user will not see error page.
from pull-request 1377
* refs/heads/upgrade/play-2.3:
Upgrade Play from 2.2.6 to 2.3.6
ProjectApp: Fix the incorrect status code for label
test: Fix url encoding bug
test: Fix RuntimeExceptions
Upgrade Play from 2.1.0 to 2.2.6
Reviewed-by: 이희구
Related Issue: https://github.com/naver/yobi/issues/811
* By adding constrains, prevent adding duplicated ProjectVisitation data.
* By removing existing duplicated data, users who have duplicated data
can see Project's resources.
Fix a bug that code browser does not show the latest pull request on
each branch.
See https://github.com/naver/yobi/issues/822 for more details about the
issue.
* dythmall-master:
issue #822 fixed
Reviewed-by: 이응준
* Upgrade sbt from 0.13.0 to 0.13.5.
* Upgrade jsmessages from 1.6.1 to 1.6.2.
* Downgrade play-2-mail from 1.0.0 to 0.9.1.
* Split project/Build.scala into build.sbt and
project/BuildConfig.scala.
* Introduce sbt-less.
* Introduce sbt-twirl, the new template engine for PlayFramework, and
fix compile errors caused by it.
* Import scala.collection.JavaConversions._ for conversion between
Java and Scala collections.
* Import java.lang_ and java.util._ to use java types.
* Use implicitJavaLang imported from play.core.j.PlayMagicForJava._
instead of lang.
* Use requestHeader imported from play.core.j.PlayMagicForJava._
instead of request.
* Specify play.data.Form in full qualified name to avoid conflict
with play.api.data.Form.
* Fix the other template errors.
* Etc
* Use Result instead of deprecated SimpleResult.
* Use java.nio.file.NotDirectoryException instead of
scalax.file.NotDirectoryException.
* Update README to say use "acvitator" command instead of "play".
* Add methods to PlayServlet to support Servlet 3.1
IMPORTANT NOTE: You should modify the version of h2database on which
Play depends from 1.3.175 to 1.3.176 in
~/.ivy2/cache/com.typesafe.play/play-jdbc_2.10/ivy-2.3.6.xml as follows:
to avoid org.h2.jdbc.JdbcSQLException because of the bug that h2database
1.3.175 cannot create or alter sequence.
When a user tries to attach a label to a project, ProjectApp.attachLabel
responses 201 if the label is created newly and attached and 204 if the
label is already attached.
But it shouldn't have work correctly because it was not possible to know
whether the label has been already attached if the label is created just
now. I have no idea why this has worked correctly until I upgrade Play
to 2.2.6.
This also fixes the condition to warn that a label is not attached
abnormaly.
* Upgrade play-jsmessages from 1.4.1 to 1.6.1
* Use com.fasterxml.jackson.databind.JsonNode instead of
org.codehaus.jackson.JsonNode;
* Use javassist 3.18.2-GA to fix the verify error
* Use Promise inteadof Result
I consulted docs/ko/Play2.2_Migraion.md
BACKWARD COMPATIBLITY: You should modify the loggers configuration in
conf/application.conf:
event-handlers = ["akka.event.Logging$DefaultLogger", "akka.event.slf4j.Slf4jEventHandler"]
to:
loggers = ["akka.event.Logging$DefaultLogger", "akka.event.slf4j.Slf4jLogger"]
