In house we've got some pretty simple m1 plugins that deal with PHP
webapps/source files:
* phpdoc reporting plugin
* php compiler/optimizer/obfuscater plugin
* some general file/resource copying goals that build a WAR-like
structure
Not that I'm a huge fan of PHP, but if a customer wants me/us to use it,
then I want a stable, repeatable build/test/deploy procedure ;)
These plugins require some enhancements so I figured I'd move the logic
to Mojos, with the understanding that I could wrap the Mojos with jelly
for continued use on m1 projects.
My questions are:
1) To test a plugin, other than Mojo unit testing, is it required
that the plugin be installed first (like m1)? Or, is there a way to
instantiate a project programmatically using a test POM and call a goal
to be tested from within the plugin development project?
2) Any pointers to an example of a wrapping a Mojo with jelly for use
with m1?
3) Are there any "gotchas" to avoid when attempting to write a single
plugin for m1 and m2? Or, should I just maintain two versions?
Also, I'm considering the possibility of adding support for a new
dependency type (phar or pear) to keep this cruft out of our SCM. Is
type support added via plugins?
Oh, most importantly, anyone know of any existing efforts such as the
above? I'd hate to reinvent the wheel.
Thanks always,
Doug
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
