You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Piotr Oktaba <pi...@coconet.pl> on 2008/06/24 10:54:54 UTC
Replacement of WAR lifecycle
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
Re: Replacement of WAR lifecycle
Posted by Milos Kleint <mk...@gmail.com>.
FYI in netbeans you can let the IDE know that your custom packaging is
basically a 'war'
http://mevenide.codehaus.org/m2-site/mevenide2-netbeans/customizations.html
no UI, but possible to set.
Milos
On 6/24/08, Piotr Oktaba <pi...@coconet.pl> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Replacement of WAR lifecycle
Posted by Arnaud HERITIER <ah...@gmail.com>.
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 <pi...@coconet.pl>
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
>