[ 
https://issues.apache.org/jira/browse/MSITE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MSITE-745.
--------------------------------
    Fix Version/s:     (was: waiting-for-feedback)
                       (was: wontfix-candidate)
       Resolution: Invalid

Then closing this. When we deploy sites we always stage outside of the tree.

> Multimodule projects staged in wrong directory
> ----------------------------------------------
>
>                 Key: MSITE-745
>                 URL: https://issues.apache.org/jira/browse/MSITE-745
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: site:stage(-deploy)
>    Affects Versions: 3.3
>            Reporter: Marcin Wisnicki
>            Priority: Major
>         Attachments: MSITE-745.zip
>
>
> All child projects are put into subdirectory that is inside subdirectory of 
> the same name, eg:
> given tree of projects:
>  * R
>  ** A
>  ** B
>  *** B1
> where R and B are aggregate projects as well as parents of their respective 
> children.
> R/pom.xml:
> {code}
>   <distributionManagement>
>      <site>
>         <id>${project.artifactId}-site</id>
>         <url>${project.baseUri}</url>
>      </site>
>   </distributionManagement>
> {code}
> site:stage should generate:
> {code}
> R/target/stagging/A/index.html
> R/target/stagging/B/index.html
> R/target/stagging/B/B1/index.html
> {code}
> but instead produces:
> {code}
> R/target/stagging/A/index.html
> R/target/stagging/B/B/index.html
> R/target/stagging/B/B1/B/B1/index.html
> {code}
> I'll try to attach example project later.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to