[
https://issues.apache.org/jira/browse/MSITE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634671#comment-17634671
]
Marcin Wisnicki commented on MSITE-745:
---------------------------------------
You're right, for some reason I assumed evaluation would happen before
inheritance but that's not the case.
Moving staging outside target implies the path would be environment specific
and set by user which is suboptimal. Target is where Maven users expects to
have all build artifacts.
Looks like I'd need a property for project root dir like discussed in MNG-7038.
Although Ideally I shouldn't have to set anything and just have this work
automagically. At least in the past Maven declared convention over
configuration as one of design goals, perhaps this changed? Current behavior is
not very helpful in multi-module projects.
> 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
> Fix For: waiting-for-feedback, wontfix-candidate
>
> 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)
