I would use the plug-in to set up test resource for integration testing
and later tear them down.
eg start a database server, run tests and stop a database server.
I currently use antrun to start the postgresql database server and later
shut it down.
The problem is that if my test fail, the database server is still
running and has to be kill manually.
I would like to be able to run an external program in such a way that
ensures the program is stopped when maven exits.
Jerome Lacoste (JIRA) wrote:
[ http://jira.codehaus.org/browse/MEXEC-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87432 ]
Jerome Lacoste commented on MEXEC-19:
-------------------------------------
Is there a use case where we don't want to bin to the process-classes ?
exec:java plugin should bind to the process-classes phase
---------------------------------------------------------
Key: MEXEC-19
URL: http://jira.codehaus.org/browse/MEXEC-19
Project: Mojo Exec Plugin
Issue Type: Improvement
Affects Versions: 1.1
Environment: maven-exec-plugin-1.1-SNAPSHOT
Reporter: Ryan Sonnek
Priority: Trivial
the exec:java plugin uses adds target/classes to the classpath, but relies on
the user to run a specific maven goal (ex: install, compile, etc) before
running the plugin. It would be better if the exec:java plugin automatically
bound to the process-classes phase to always compile the classes in need.
