What you're seeing as overlap is a mixture of concerns in the invoker
plugin. The verifications beanshell really needs to be migrated out
to some sort of proper integration-testing plugin (or, even better, a
plugin that unites invoker and verifier under a common
configuration...then extend the verifier with the invoker's beanshell
functionality). Regardless, the invoker plugin can be used for any
sort of scenario where you need to fork a new maven process. I've
personally used it to proxy secondary builds in some sticky client
use cases. You don't have to use the beanshell script to verify the
build, it's just an [admittedly confusing] option.
-john
On Dec 11, 2007, at 6:28 PM, Dan Fabulich wrote:
Forgive me if I'm picking at a sore spot, but can someone help me
understand the difference/overlap between maven-invoker and maven-
verifier?
As I understand it, they both do roughly the same thing, except one
of them is a Maven plugin where you write your test in a goals.txt
file + beanshell, and the other is meant to be run programmatically
from a JUnit test. Is that essentially correct?
(Whereas maven-verifier-plugin is another beast entirely, simply
checking for the presence/absence of certian files.)
Am I right in thinking that, despite their substantial overlap,
maven-verifier and maven-invoker share no code?
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
rss: http://feeds.feedburner.com/ejlife/john
