[MSITE-687] wrong site stage location when parent pom (not in reactor) has same site

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2
• Fix Version/s: 3.3
• Component/s: site:stage(-deploy)
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 25/Apr/13 12:26
• Updated: 09/May/13 16:11
• Resolved: 09/May/13 15:08

Description

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

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...)

Issue Links

• relates to: MSITE-669 site:stage creates incorrect structure when module paths contains sets of "../"