You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions, Inc. at Cisco)" <jp...@cisco.com> on 2006/07/13 23:07:53 UTC

Not using pom.xml

 
Hi,
 
Is there any way I can force my custom made plugin to not use pom.xml.
There is a parameter @requiresProject (which is used in archetype), this
works fine if there is no pom.xml. But if pom is available the plugin
will use it.
What I want is even if the pom.xml is available do NOT use it.
 
Please let me know.
 
Thanks
-Jagan
 
 

Re: Not using pom.xml

Posted by Eric Redmond <er...@gmail.com>.
I don't believe that is an option. The question is... why? Is it because you
want to always require the user to enter command-line parameters?

Thanks;
Eric

On 7/13/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions, Inc.
at Cisco) <jp...@cisco.com> wrote:
>
>
> Hi,
>
> Is there any way I can force my custom made plugin to not use pom.xml.
> There is a parameter @requiresProject (which is used in archetype), this
> works fine if there is no pom.xml. But if pom is available the plugin
> will use it.
> What I want is even if the pom.xml is available do NOT use it.
>
> Please let me know.
>
> Thanks
> -Jagan
>
>
>
>


-- 
Eric
http://codehaus.org/~eredmond