I'm having a heck of a time with our build since we've been required to use a parent pom.xml that has it's own distributionManagement section. The plan is to not allow us to define our own distributionManagement - but relying on the parent for our <site> definition seems to have wreaked all kinds of havoc.
I'd hope that the -DstagingDirectory="c:\whatever" would enable us to force the build there, but it seems to keep tacking on the <site> directory, but not as a whole - rather in pieces, and not reliably. Is there some trick to doing a mvn site:stage or mvn site:stage-deploy where I can have complete control over where the site is - overriding the entire <site> definition in the <distributionManagement> section of the pom.xml??? -- View this message in context: http://old.nabble.com/Forcing-maven-site-plugin-to-override-replace-distributionManagement-tp27854110p27854110.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
