The reason is, the dependencies are resolved based on where we are running the build i.e., which branch in clear case. For diff branches I may need to select diff versions of the artifact which my plug-in is automated to take care.
For this to work, I don't want maven to start looking for the dependencies and download once you execute the maven goal. My plug-in will update the pom file dependencies on the fly with the exact version we need to use and then give control to maven to do its work. This can achieved if I can disable the dependencies resolution at the starting or not use the pom file itself. Do you see anyway to achieve this. Thanks -Jagan -----Original Message----- From: Eric Redmond [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 2:43 PM To: Maven Developers List Subject: Re: Not using pom.xml 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) <[EMAIL PROTECTED]> 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
