I had a similar issue and I added the parameter "packaging" in the maven-eclipse-plugin to use a custom packaging but to have the behavior of another one. http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#packaging The problem is that in maven 2.0.X we don't have actually an inheritence of packaging.
Arnaud On Tue, Jun 24, 2008 at 10:54 AM, Piotr Oktaba <[EMAIL PROTECTED]> wrote: > Hi, > > I have following problem. > I would like to write my own maven2 war plugin with my own lifecycle. > Currently available maven-war-plugin does not fit my requirements. I > have chosen war packaging instead of my own (for example portal) because > I do not want to lose support from other tools (for example maven plugin > for netbeans or maven-eclipse-plugin - the last one doesn't generate > project if packaging is non standard). > However, only way of replacement war lifecycle which I have found is > commenting part of components.xml file in uberjar file in maven2 > installation and provide my own component definition in plugin. Is there > any more ellegant solution than commenting that file? > > Cheers, > Piotr Oktaba >
