For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 8 replies, 6 voices, and was last updated 15 years, 10 months ago by
.
-
Posts
-
I am using MyEclipse 7.5 right out of the box on a Windows XP 32bit laptop.
I have created an Eclipse project from a Maven project using the eclipse plugin for Maven. The project has a javanature, webnature, mavennature, and springnature.
I am trying to configure Eclipse to automatically update the exploded web application when a file is modified.
Invoking ‘war:inplace’ works fine when I right-click on the pom.xml, and select Run As > “Maven Build…” with the goal set to ‘war:inplace’.
I have configured Maven4MyEclipse to invoke the following goals when a resource changes: “process-resources resources:testResources war:inplace”. The problem is, I get the following error when MyEclipse tries to run war:inplace after a file changes.
9/17/09 5:28:42 PM CDT: [INFO] Assembling webapp webapp in C:\Documents and Settings\swick\Workspaces\MyEclipse\com.fmcdistributor\src\main\webapp
9/17/09 5:28:42 PM CDT: Build errors for com.fmcdistributor; org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal ‘org.apache.maven.plugins:maven-war-plugin:2.0.2:inplace’: Mojo execution failed.Can anyone explain why this is happening, and/or how to fix it?
Thanks.
Stephen
Yeah,
My Web Project is deployed to a Tomcat server in MyEclipse. I am trying to configure Eclipse to update the deployed webapp whenever a change is made, so that I can test the changes immediately in my web browser.
Does that make sense?
Stephen
stephen, this is an interesting idea. We might be trying to solve a similar issue (https://www.genuitec.com/forums/topic/maven2-war-project-not-honoring-pom-dpndncy-scope-on-deploy/&highlight=maven2+war).
Have you tried adding “-e” to the end of your goals within the launch config? Eg “process-resources resources:testResources war:inplace -e”. This will cause maven to spit out a few more details that might help with tracking down the root cause.
