|[2.0] Integrating Play 2.0 applications in a Maven-based build process||Clement Escoffier||4/1/12 9:51 AM|
I know that Play 2 is promoting SBT, but here it's not the point. We're heavily relying on Maven, and so the question was: how do we integrate Play 2 app in our current build process (Apache Maven, Jenkins, Sonatype Nexus, deployment using Puppet).
So, I've created a play2-maven-plugin to integrate play 2 app within Maven builds. It's pretty simple, and actually don't do much except wrapping play 2 calls.
It supports dependency management, compilation, test and packaging (relying on dist).
The code is on Github: https://github.com/cescoffier/maven-play2-plugin
|unk...@googlegroups.com||7/27/12 2:29 AM||<This message has been deleted.>|
|This message has been hidden because it was flagged for abuse.|
|Re: [play-framework] [2.0] Integrating Play 2.0 applications in a Maven-based build process||Clement Escoffier||7/29/12 1:48 AM|
There is a quiskart guide here: http://cescoffier.github.com/maven-play2-plugin/maven/release/quickstart.html
On 27.07.2012, at 11:29, Figroc Chen wrote:
|Re: [play-framework] [2.0] Integrating Play 2.0 applications in a Maven-based build process||Clement Escoffier||7/29/12 1:57 AM|
There are several reasons for using Maven in my case:
1) my team knew Maven, and don't really have time to learn SBT.
2) the play part is just one part of the system we developed, the rest is using Maven, so being able to build everything in one command was better/simpler/faster.
3) Using Jenkins / Nexus with SBT is possible but require quite some configuration, which was already done with Maven (deployment target, profiles, authentication, unit test / integration tests / deployment tests reports…)
4) The release process and continuous delivery process are really important points for me. We have hard/strict release process and continuous delivery pipelines. Re-implementing them with SBT for only one part of the system was definitely too costly.
So, in my case, switching to Maven is to reduce the cost. However we still use the Play 'development' mode (hot-reload), but the 'real' build use Maven (executed by Jenkins), and it's the Maven build which is deployed on the staging / prod system. So actually, we have the best of both world).
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/pHiR_N_XPlsJ.
|Re: [play-framework] [2.0] Integrating Play 2.0 applications in a Maven-based build process||Figroc Chen||7/29/12 2:48 AM|
I have managed the build process using mvn tool with the plugin. But Eclipse complains constantly, saying that it fails on the compile phase and copydependecy phase. (I've posted detailed message in the plugin 1.2.0 announcement thread. I can't access that info right now. Sorry for the inconvenience.)
|Re: [play-framework] [2.0] Integrating Play 2.0 applications in a Maven-based build process||Figroc Chen||7/29/12 8:05 PM|
The post I've mentioned previously has been deleted somehow. I'll repost the detailed error messages here. Please let me know if it's inappropriate.
Plugin execution not covered by lifecycle configuration: de.akquinet.innovation.play2:play2-maven-plugin:1.2.0:compile (execution: default-compile, phase: compile) pom.xml /net.svr.sms line 40 Maven Project Build Lifecycle Mapping Problem
Plugin execution not covered by lifecycle configuration: de.akquinet.innovation.play2:play2-maven-plugin:1.2.0:copy-dependencies (execution: default-copy-dependencies, phase: process-resources) pom.xml /net.svr.sms line 40 Maven Project Build Lifecycle Mapping Problem
From line 40 from the pom.xml is:
BTW, the OS is Windows Server 2008 R2 x64, m2e version is 220.127.116.1120530-0009.
On Sunday, July 29, 2012 5:48:06 PM UTC+8, Figroc Chen wrote:
|Re: [play-framework] [2.0] Integrating Play 2.0 applications in a Maven-based build process||Clement Escoffier||7/31/12 1:06 AM|
Did you try without the maven-compiler-plugin ? The compilation is done by play.
--To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/L_kkFvc8nZoJ.