The other thing you can do is override the distributionManagement
section of the module B so that deploy just puts it somewhere local like
file://${basedir}/target instead of the remote repo-----Original Message----- From: Michael [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 10:38 AM To: Maven Users List Subject: Re: Deploying only some modules Wendy Smoak wrote: > On Thu, May 8, 2008 at 10:23 AM, Michael <[EMAIL PROTECTED]> wrote: > >> I do have a multimodule project: >> >> pom -- (root) >> | jar (module A) >> | war (module B) >> >> The war file is just a demo and in my opion not an artifact which should be >> on central. > > If the jar has a <parent> element, then you'll probably need to deploy > the root pom in addition to the jar. You can use -N (non-recursive). Hi Wendy, the jar has a <parent> element. Is it mandatory to deploy the root pom? For some reason site.xml is deployed too. > It's not released yet, but as of v2.4 the deploy plugin can be > configured to skip deployment of individual modules. > http://jira.codehaus.org/browse/MDEPLOY-63 Let's wait for 2.4 :-( Any release timeframe? Thanks, Mike -- <NO> OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
