[ http://jira.codehaus.org/browse/MNG-1922?page=comments#action_85444 ] Kenney Westerhof commented on MNG-1922: ---------------------------------------
You may be right - it can only execute maven projects, embedded (that's where most original embedder code came from actually ;)). this plugin actually abuses the maven build lifecycle, using a pom to configure it, to set up pre- and post- test hooks, in order to set up and tear down the integration environment. This can be done using maven plugins to, for instance, deploy your artifact (that's why it uses maven projects so it knows about your artifact), start a container, and later turn it off. This can all be done in code too, but this approach leverages all of maven and maven's plugins to ease the work. I think it's just a matter of properly documenting it. Btw, it doesn't affect any maven version so this should probably be moved to some other project. Anyway, the host of all it/test plugins out there is currently undergoing discussion to delete/merge them, so we better wait what happens with that. > Rename maven-it-plugin plugin as its name implies it is for performing > integration tests in general > --------------------------------------------------------------------------------------------------- > > Key: MNG-1922 > URL: http://jira.codehaus.org/browse/MNG-1922 > Project: Maven 2 > Issue Type: Task > Components: integration tests > Affects Versions: 2.0.1 > Reporter: Vincent Massol > Fix For: 2.0.x > > > The it plugin is really meant to perform functional tests of plugins and as > such should be renamed. > Ideas: > * maven-plugin-it-plugin > * maven-test-plugin-plugin > *Another idea is to include its feature in the plugin plugin under a > plugin:test mojo.* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
