wouterhardeman / play2-maven-plugin

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

Changing packaging to WAR breaks module #26

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Play2 Maven plugin stops compiling or reacting to explicit invocations if you 
change packaging to WAR.

Even though adding com.github.play2war servlet container artifacts to the build 
allow mvn war:war to produce a Tomcat friendly WAR file.

Original issue reported on code.google.com by a...@activelogic.eu on 18 Feb 2014 at 12:47

GoogleCodeExporter commented 8 years ago
Changing packaging to "war" is not the right way. "play2" mojos work only for 
"play2" packaging. Add maven-war-plugin's "war" mojo execution to "play2" 
packaging instead.

http://code.google.com/p/play2-maven-plugin/source/detail?r=342 - two versions 
of "helloworld" example project with maven-war-plugin integration added: for 
Servlet specification 2.5 and 3.0.

I haven't tested if produced wars deploy yet. Can you try similar configuration 
in your project and write about results here?

Remember to choose right version of "play2-war-core-servlet[25|30]_2.10" 
dependency for your Play! version - 
https://github.com/dlecan/play2-war-plugin/tree/develop

Original comment by gslowiko...@gmail.com on 19 Feb 2014 at 8:26

GoogleCodeExporter commented 8 years ago
http://code.google.com/p/play2-maven-plugin/source/detail?r=343 - two versions 
of "helloworld" example project with maven-war-plugin integration added: for 
Servlet specification 2.5 and 3.0 - dependency fixed.

Original comment by gslowiko...@gmail.com on 26 Feb 2014 at 3:31

GoogleCodeExporter commented 8 years ago
Servlet 2.5 project 
https://play2-maven-plugin.googlecode.com/svn/trunk/test-projects/play22/scala/h
elloworld-war-servlet-2.5 tested with Apache Tomcat 7.0.52

Servlet 3.0 project 
https://play2-maven-plugin.googlecode.com/svn/trunk/test-projects/play22/scala/h
elloworld-war-servlet-3.0 tested with Apache Tomcat 8.0.3

Both work.

Original comment by gslowiko...@gmail.com on 26 Feb 2014 at 3:34

GoogleCodeExporter commented 8 years ago

Original comment by gslowiko...@gmail.com on 11 Apr 2014 at 7:01

GoogleCodeExporter commented 8 years ago
https://code.google.com/p/play2-maven-plugin/source/detail?r=691 - 
"play2-war-core-servlet[25|30]_2.10" dependencies version upgraded from 
"1.2-beta4" to "1.2" and scope changed from "compile" to "runtime" (these 
dependencies are not required to build the project) in example projects.

Original comment by gslowiko...@gmail.com on 22 Aug 2014 at 7:06

GoogleCodeExporter commented 8 years ago
https://code.google.com/p/play2-maven-plugin/source/detail?r=695 - WAR 
packaging example projects (for Play! 2.2.x) moved from "war" directory to: 
"play21/war", "play22/war" and "play23/war" and customized for different Play! 
versions ("2.1.x", "2.2.x" and "2.3.x").

Original comment by gslowiko...@gmail.com on 24 Aug 2014 at 10:32

GoogleCodeExporter commented 8 years ago
https://code.google.com/p/play2-maven-plugin/source/detail?r=699 - WAR 
packaging example projects (for Play! 2.2.x) moved from "war" directory to: 
"play21/war", "play22/war" and "play23/war" and customized different Play! 
versions ("2.1.x", "2.2.x" and "2.3.x") - fixed bug accidentally introduced in 
Play! 2.1.x version.

Original comment by gslowiko...@gmail.com on 24 Aug 2014 at 12:21