[jira] [Commented] (MSITE-1010) site-deployment for POM projects does not create project directories in site repository

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863549#comment-17863549 ] 

ASF GitHub Bot commented on MSITE-1010:
---------------------------------------

Bukama opened a new pull request, #194:
URL: https://github.com/apache/maven-site-plugin/pull/194

   Proposed commit message:
   
   ```
   [MSITE-1010] Add documentation how site repository inheritance
   
   More information including an example how the site repository configuration is inherited,
   when using a parent-pom.
   
   closes #MSITE-1010
   
   ```
   
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
   
    - [x] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MSITE) filed 
          for the change (usually before you start working on it).  Trivial changes like typos do not 
          require a JIRA issue.  Your pull request should address just this issue, without 
          pulling in other changes.
    - [x]  Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[MSITE-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MSITE-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of the 
          commit message.
    - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will 
          be performed on your pull request automatically.
    - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`).
   
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
   please ask on the developers list.
   
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   you have to acknowledge this by using the following check-box.
   
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
   
    - [x] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
   
   




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