By the way, please add [m2] to your subject so other Maven 2 developers
would take note. They might skip/miss out on your email, thinking it's a
m1 question. :-)
Regards,
John
Michael Thompson wrote:
All,
So we are delving into the world maven2 and eclipse plugins. In order
to package my plugin, I think I need a new artifact type since the
standard jar packaging won't suffice. Just FYI, eclipse plugins are
actually zip files that contain your class files in a contained jar,
dependency jars, a special manifest and your resources.
So my questions are:
1. Is a new artifact type needed? Or can I do this by having a
really fancy pom.xml?
2. If a new artifact type is needed, I can envision a couple places
in the build life cycle that I need to override (process-resources and
package). Would the standard approach be to create one plugin for the
artifact lifecycle override (components.xml) and 2 more plugins for the
2 stages of the life cycle I want to override?
Thanks in advance!
--m
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
