Hi 陈思淼, the second way is the one to go. Implement your own lifecycle. "overriding" an existing lifecycle mapping is not simple (if even possible in plexus), and anyway overriding a plugin is not simple because of doclets pointing to private fields and not being retained in subclasses.
Simone 陈思淼 wrote: > I want to modify the war-plugin's source code and generate a new plugin in > my own groupId and artifactId to do something accouding to my own needs. > can my own maven-war-plugin to override of the original maven-war-plugin > when build war project? > If not, can I define a new packaging type called twar, to bind with my own > plugin? > > -- Simone Gianni CEO Semeru s.r.l. Apache Committer MALE human being programming a computer http://www.simonegianni.it/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
