Now initialization looks like:
Play.frameworkPath = playHome;
Play.init( applicationPath, playId );
if ( !Play.started )
{
Play.start();
}
Although "applicationPath" is initialized, when I want to use it in
"log4j.properties" configuration file like this:
log4j.appender.Rolling.File=${application.path}/logs/application.log
it does not work.
It works in pure Play!, because Play's Python scripts add "application.path"
and "play.id" System property setting parameters ("-D" JVM options) to Java
invocation.
The same behavior is implemented in Play! server starting mojos of this Maven
plugin from long time, but it's not implemented in Play! Surefire provider.
Original issue reported on code.google.com by gslowiko...@gmail.com on 19 Mar 2013 at 2:32
Original issue reported on code.google.com by
gslowiko...@gmail.com
on 19 Mar 2013 at 2:32