search

raby / play2-maven-plugin

Automatically exported from code.google.com/p/play2-maven-plugin
0 stars 0 forks source link

Improve Run and Start mojos #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Now "process-classes" is called automatically before actual execution of 
"play2:run" and "play2:start" mojos logic.

This was done this way because it works similarly in SBT. The purpose is to be 
sure the project runs with current sources.

This is sometimes not convinient:
1. You know, you compiled everything before ("mvn process-classes"), and don't 
want to waste time for empty recompilation.
2. In multimodule projects when working without installing to local repository, 
you have to call "mvn process-classes play2:run", so "process-classes" is 
executed twice.

If you want the old logic just call "mvn process-classes play2:run" or "mvn 
process-classes play2:start" instead of "mvn play2:run" or "mvn play2:start".

Original issue reported on code.google.com by gslowiko...@gmail.com on 6 Apr 2014 at 8:20

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/play2-maven-plugin/source/detail?r=378 - "@Execute( 
phase = LifecyclePhase.PROCESS_CLASSES )" annotation removed.

Original comment by gslowiko...@gmail.com on 6 Apr 2014 at 8:23

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/play2-maven-plugin/source/detail?r=379 - allow calling 
"play2:run" / "play2:start" mojos without calling at least "compile" first 
(without having project's artifact set).

Original comment by gslowiko...@gmail.com on 6 Apr 2014 at 8:27

GoogleCodeExporter commented 9 years ago

Original comment by gslowiko...@gmail.com on 11 Apr 2014 at 6:58

GoogleCodeExporter commented 9 years ago 
https://code.google.com/p/play2-maven-plugin/source/detail?r=1142 - 
"executedProject" parameters are obsolete after removing "@Execute( phase = 
LifecyclePhase.PROCESS_CLASSES )" annotation in rev.378 
(https://code.google.com/p/play2-maven-plugin/source/detail?r=378).

Original comment by gslowiko...@gmail.com on 14 Nov 2014 at 9:05

GoogleCodeExporter commented 9 years ago 
https://code.google.com/p/play2-maven-plugin/source/detail?r=1144 - when 
constructing classpath always use "classes" directory (instead of project's 
artifact - "jar" file), for projects with separate "assets" jar all assets are 
present in "classes" directory, but they are not present in project's jar file 
("assets" jar has to be added to classpath as well).

Original comment by gslowiko...@gmail.com on 14 Nov 2014 at 9:32