[
https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861002#comment-17861002
]
Matthias Bünger commented on MSITE-1010:
----------------------------------------
Thanks, they were also helpfull and I think I got it now.
With this knowledge the docs on the [Building multi-module
sites|https://maven.apache.org/plugins/maven-site-plugin/examples/multimodule.html]
become kinda clear(er), I still see some pitfalls there in terms of the
inheritance together with a META-POM that you have to be aware that "the
topmost project" is not your parent POM of the multi-module project (what I
think about when I read about multi-module projects), but the META-POM as the
parent of the parent POM. I mean yes one of the "notes" listed there tells
about the inheritances, but I have not put it in the right context (esp. as the
"site" {{<distributionManagement>}} works different as the release/snapshot one.
What do you think? Shall I add a short documentation page about the inheritance
of the site distribution together with using a META-POM? The [siteDistribution
POM reference page|https://maven.apache.org/pom.html#Site_Distribution] doens't
make this difference clear too (in my opinion). But I totally understand when
you think it's clear enough and close the issue.
> site-deployment for POM projects does not create project directories in site
> repository
> ---------------------------------------------------------------------------------------
>
> Key: MSITE-1010
> URL: https://issues.apache.org/jira/browse/MSITE-1010
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 3.12.0, 4.0.0-M14
> Environment: Nexus, since at least Maven 3.6.3 (not tested with 3.9.7
> or 4.0.0-beta)
> Reporter: Matthias Bünger
> Priority: Minor
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Attachments: pom.xml, webdav.txt
>
>
> I noticed the following issue while updating the plugins in our teams
> META-POM and could backtrack it at least until 3.12 but might be an even
> older issue. Havn't checked 4.0.0-M15 but from the releases notes I doubt it
> is fixed.
> When you do "site-deploy" for a single module or multi module project the
> site files (.html, css-folders, etc.) are stored in the site-repository (we
> have current Nexus version) within a subfolder with the name of the project,
> e.g
> {code}
> / (root of site-repository)
> /- project-A
> /css
> report.html
> /- project-B
> /css
> report.html
> /project-C
> {code}
> If you do the same for a "POM" project (e.g. a META-POM or BOM) the site
> files are all stored at root level (instead of creating a project folder) and
> ofc overwriting the ones from other POM-projects:
> {code}
> / (root of site-repository)
> /css
> /project-A
> /project-B
> /project-C
> report.html
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
