[ http://jira.codehaus.org/browse/MINVOKER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118945
]
skaze edited comment on MINVOKER-22 at 1/6/08 2:56 PM:
------------------------------------------------------------
We use the maven-component-it-plugin for this but see [Brett's comparison matrix|http://www.nabble.com/More-on-plugin-integration-testing-td14503424s177.html#a14503424]
of all he different testing plugins/harnesses and approaches. Also see the codehaus 'shitty'
plugin (yes that's its name) that does attempt to unify invoker and install/component-it-plugin
functionality.
was (Author: skaze):
We use the maven-component-it-plugin for this but see Brett's comparison matrix of all
he different testing plugins/harnesses and approaches. Also see the codehaus 'shitty' plugin
(yes that's its name) does attempt to unify invoker and install/component-it-plugin functionality
> Add feature to install plugin to a local repository.
> ----------------------------------------------------
>
> Key: MINVOKER-22
> URL: http://jira.codehaus.org/browse/MINVOKER-22
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
> Affects Versions: 1.1
> Reporter: Paul Gier
> Fix For: 1.2
>
>
> Currently if I want to test a maven plugin, I have to use the install plugin to install
the jar into a temporary repository location. It would be helpful if there was a way that
the invoker plugin could do this by itself instead of needing to use the install plugin.
--
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
|