[ https://jira.codehaus.org/browse/MSITE-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MSITE-687. ------------------------------- Resolution: Fixed Assignee: Herve Boutemy IT added in [r1480749|http://svn.apache.org/r1480749] new parameter added in [r1480752|http://svn.apache.org/r1480752] to permit default value override > wrong site stage location when parent pom (not in reactor) has same site > ------------------------------------------------------------------------ > > Key: MSITE-687 > URL: https://jira.codehaus.org/browse/MSITE-687 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:stage(-deploy) > Affects Versions: 3.2 > Reporter: Herve Boutemy > Assignee: Herve Boutemy > Fix For: 3.3 > > Attachments: MSITE-687.zip > > > problem found when staging Maven 3.1 and Doxia 1.4: root site calculation > doesn't restrict to current reactor, but goes as far as the deploy site is > the same > for Maven 3.1-SNAPSHOT, the consequence wasn't too much: it just staged in > target/staging/ref/3.1-LATEST so there was an [easy > workaround|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=297bbca90f3d9d8b23d69d2493476b0df81d1de1] > for Doxia 1.4, since the Doxia POM distributionManagement url is > scm:svn:https://svn.apache.org/repos/infra/websites/production/maven-doxia/content/doxia-archives/doxia-LATEST > and the root parent resolved is > scm:svn:https://svn.apache.org/repos/infra/websites/production/maven/content, > the calculated relative path is > ../../maven-doxia/content/doxia-archives/doxia-LATEST, then calculated > staging directory is maven-doxia/content/doxia-archives/doxia-LATEST (yes, > not in target...) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira