Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.1
-
Fix Version/s: None
-
Component/s: Integration Tests
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
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.
Activity
Hi Kenney,
Apologies if I'm wrong but I thought the it plugin's goal was to execute Maven2 projects and I can't think of a use case different than for testing m2 plugins. I don't see how it can be used as a general purpose integration test plugin. I've probably missed something... 
Thanks
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.
I didn't intend it to JUSt test plugins - it runs after the artifact is built and hence can be used to deploy wars
and test them.
Close?