Which part is it that you need to use in the dependency plugin? The actual copying and unpacking is mostly delegated to the maven-archiver component.
-----Original Message----- From: Kallin Nagelberg [mailto:[EMAIL PROTECTED] Sent: Saturday, December 29, 2007 4:03 PM To: Maven Users List Subject: Plugins within plugins: best practices Hello everyone, I've created a standalone plugin in which I'm doing some unpacking/copying of artifacts in addition to a few other things. I would like to defer the unpacking/copying operations to the maven dependency plugin for obvious reasons. Has anyone tried creating and configuring a plugin instance within another plugin and calling the execute method directly? I'm tempted to try this, but am worried about potential side effects. I figure I can try to build the plugin instance with what components I've already got within my plugin and pass them along. Is there a better way to use this, perhaps some sort of core maven plugin builder? Any help would be greatly appreciated. Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
