Things to do:
a) create common base class for "start" (for standalone use) and "start-server"
(used in "play" lifecycle for starting Play! server before Selenium integration
testing) mojos
b) add additional "start" mojo configuration options:
- add "spawn" option (<a href="http://ant.apache.org/manual/Tasks/java.html">Ant Java task documentation</a>), now it's always spawning started server process (in contrast to "start-server" mojo which is never spawning),
- add "startSynchro" option, when set "start" mojo waits for "http://localhost:${server.port}" URL availability after starting (this functionality was always present in "start-server" mojo),
- add "startWithTests" option, used to choose between "playId" and "playTestId" as starting server profile (similar to "precompileTests" for "precompile" mojo).
Original issue reported on code.google.com by gslowiko...@gmail.com on 14 May 2012 at 6:30
Original issue reported on code.google.com by
gslowiko...@gmail.com
on 14 May 2012 at 6:30