Doug Douglass wrote:
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.
Good idea!
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?
For now, we do separate projects for testing after installation (the
integration tests maven-core-it). There is a new plugin being worked on:
maven-it-plugin - which will streamline that in a way. As the embedder
improves, that will probably allow testing without installation.
We have work to do on this - if you have any suggestions - feel free to
discuss them here.
2) Any pointers to an example of a wrapping a Mojo with jelly for use
with m1?
Actually, not wrapping a mojo directly. We have some plugins like the m1
scm plugin, that wraps shared libraries making it similar to the m2 scm
plugin.
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?
Try and avoid dependencies on m2 specific libraries in the mojo as it
will hinder using it from m1.
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?
yep
Oh, most importantly, anyone know of any existing efforts such as the
above? I'd hate to reinvent the wheel.
Not that I've heard.
Thanks,
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
