Hiya folks... some of you may have noticed the shitty-maven-plugin in
the mojo-sandbox. This was my solution to Maven plugin integration
testing, which I really needed to help ensure the quality of releases
of the Groovy, Selenium, JSP Compiler and Retrotranslator Maven 2
integration.
A week or so ago, I was talking about it in #maven and several folks
expressed interest in the plugin (as well as site docs too :-P), and
well, I think that it may be time to move it out of the mojo-sandbox
and make an initial release of it.
The genesis of the plugin came about when I first started looking
into how to test my plugins, and I looked at a lot of existing
plugins (mojo and maven) and found a horde of different solutions,
some that worked and many that didn't... and none of them really met
my needs of easy of use and certainty of which artifact I was
actually testing. I first started out using a verbose profile that
invoked the maven-clean-plugin:clean and then maven-install-
plugin:install-file and then maven-invoker-plugin:run, though
eventually ran into problems with the invoker:run goal freaking out
when no src/it directory existed (as was the case for intermediate
pom modules which served to organize other jar and maven-plugin
modules). And then well, there was the issue of all that config and
a few other little wrinkles. So, I decided that it would be easier
to simply craft a new plugin that did exactly what I needed with a
very terse configuration... and here begins the Super Helpfull
Integration Testing ThingY (SHITTY) Maven Plugin... aka the shitty-
maven-plugin.
I actually did spend quite a bit of time trying to figure out what
the heck to call it... and maybe I had a few too many beers, and
ended up with shitty, and well... it made me laugh, and I kinda like
cheesy acronyms like that too.
This plugin has really helped me to implement a common integration
test system for my all of my Maven plugins... which simple works,
tests exactly what is being produced by the current project and
well... I'm not sure I can live without it anymore.
I think that other folks may find this very useful for their own
Maven plugin testing, as well as for other types of integration
testing. As mentioned before, several folks have expressed interest,
and I think that its time to promote it out of the sandbox. I'm
going to add some site docs and publish them in the next day or so
for review... as I've yet to add anything, since I initially wrote
this for my own usage, and generally point folks that are interested
in it to the src of the Groovy integration, which shows how its used
quite easily.
I know there are many other plugin testing plugins out there, though
I'm not sure which ones are stable/living/functional or which ones
actually do the things that I need them to do for my plugins
integration tests. I think we eventually need to come up with a
single solution for src/it muck... but for right now this plugin does
*exactly* what I want... and is really key to keeping the Groovy,
Selenium, Retrotranslator and JSP compiler plugins functioning
correctly as they are modified over time. I am willing to look at
consolidating/merging features into a uber src/it plugin at some
point, but for right now I'd rather just promote this puppy and move
on to other more interesting works.
So... is there any objection to promoting the shitty-maven-plugin out
of the mojo-sandbox?
If you object to the name, I understand, and I'm open to new ones...
Thanks for reading!
:-)
Cheers,
--jason
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
