--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/IScdweI_eOgJ.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.
Hi,For application composed by one project, yes it does.For aggregated projects, we still have some work to do.Regards,Clement
On 02.07.2012, at 06:03, Nilanjan wrote:
Good stuff. Does it pick up changes automatically like Play/SBT does?
Nilanjan
On Sunday, July 1, 2012 1:40:13 AM UTC-7, clement escoffier wrote:Hi,I'd like to announce the new play2-maven-plugin version (1.2.0). This version is available from Maven Central.
Changelog:
* Support of the latest Play Framework (2.0.2)
* Support of homebrew installation (for Mac)
* Support Maven directory structure (src/main…)
* Find the play executable from the system path
The documentation is available on http://cescoffier.github.com/maven-play2-plugin/maven/release/Regards,Clement--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/IScdweI_eOgJ.
To post to this group, send email to play-framework@googlegroups.com.
To unsubscribe from this group, send email to play-framework+unsubscribe@googlegroups.com.
Regarding IDE support as mentioned in the FAQ, specifically using Eclipse with Scala IDE, m2eclipse, and m2eclipse-scala. I'm trying to get this all to work with a sample Play! project using Scala. I can't seem to resolve compilation errors (in the editor) from statements like: views.html.index("Your new application is ready.").Is it possible to make this plugin perform the compilation step that generates target/scala-2.9.1/main contents? If I clean the project (emptying target) then build (again, from the IDE), none of the Play! generated files appear there. I've tried adding executions to the play2-maven-plugin configuration.But even when they are there (built from the command line), no approach I've tried (using build-helper-maven-plugin, and the addSource option for maven-scala-plugin) works for making that source path visible to Scala IDE.I'm staying light on details to see if you've got any thoughts on how to make this setup work correctly. And please let me know if I should repost in another forum. Thanks in advance!
(Rephrased my previous post.)
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/mIqNp5CDouMJ.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
Thanks Clement!Few questions though:- i can't manage to get the conf directory changed. while doing what you suggested, the src/main/conf/application.conf is not loaded. should i direct to the specific file somehow (other then setting confDirectory as mentioned in the doc)?
- how do i start it in production?
On Sunday, July 1, 2012 11:40:13 AM UTC+3, clement escoffier wrote:Hi,I'd like to announce the new play2-maven-plugin version (1.2.0). This version is available from Maven Central.
Changelog:
* Support of the latest Play Framework (2.0.2)
* Support of homebrew installation (for Mac)
* Support Maven directory structure (src/main…)
* Find the play executable from the system path
The documentation is available on http://cescoffier.github.com/maven-play2-plugin/maven/release/Regards,Clement
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/hVOf-T5jxHgJ.
Hi,
To post to this group, send email to play-framework@googlegroups.com.
To unsubscribe from this group, send email to play-framework+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/7Qrsjljn6CkJ.
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
[INFO] --- play2-maven-plugin:1.2.0:clean (default-clean) @ my-project ---
'java' is not recognized as an internal or external command,operable program or batch file.
[INFO] [play2:compile {execution: default-compile}]
/path/to/play/framework/build: line 11: java: command not found[INFO] ------------------------------------------------------------------------[ERROR] BUILD ERROR
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/iYRoc74cnyoJ.
Hi,
To post to this group, send email to play-fr...@googlegroups.com.
To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.
get the following error when I do "mvn clean install"
execute-tests: java.lang.reflect.InvocationTargetException
[ERROR] Failed to execute goal de.akquinet.innovation.play2:play2-maven-plugin:1.2.0:test (default-test) on project XXX: Error during compilation: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal de.akquinet.innovation.play2:play2-maven-plugin:1.2.0:test (default-test) on project XXX: Error during compilation
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during compilation
at de.akquinet.innovation.play.maven.Play2TestMojo.execute(Play2TestMojo.java:88)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:377)
at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
at de.akquinet.innovation.play.maven.Play2TestMojo.execute(Play2TestMojo.java:83)
... 21 more
Ubuntu 12.04 LTS
java version 1.7.0_03
play 2.0.2
maven 3.0.4
pom.xml
...
<repositories>
<repository>
<id>typesafe</id>
<url>http://repo.typesafe.com/typesafe/releases/</url>
</repository>
</repositories>
<build>
<!-- Play source directory -->
<sourceDirectory>app</sourceDirectory>
<testSourceDirectory>test</testSourceDirectory>
<plugins>
<plugin>
<groupId>de.akquinet.innovation.play2</groupId>
<artifactId>play2-maven-plugin</artifactId>
<version>1.2.0</version>
<extensions>true</extensions>
</plugin>
</plugins>
</build>
<dependencies>
<!-- Play Framework Dependencies -->
<dependency>
<groupId>play</groupId>
<artifactId>play_2.9.1</artifactId>
<version>2.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>play</groupId>
<artifactId>play-test_2.9.1</artifactId>
<version>2.0</version>
<scope>provided</scope>
</dependency>
</dependencies>
...
appreciated!
On Sunday, July 1, 2012 1:40:13 AM UTC-7, clement escoffier wrote:
--
You received this message because you are subscribed to the Google Groups "play-framework" group.
To view this discussion on the web visit https://groups.google.com/d/msg/play-framework/-/w3UOdcl7wtsJ.