Matthias Bünger opened MSITE-1010 and commented

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

/ (root of site-repository)
  /- project-A
   /css
   report.html
  /- project-B
   /css
   report.html
  /project-C

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:

/ (root of site-repository)
 /css
 /project-A
 /project-B
 /project-C
report.html

Affects: 3.12.0, 4.0.0-M14

Attachments:

• pom.xml (26.50 kB)
• webdav.txt (3.04 kB)

Issue Links:

• MSITE-1012 Clean up notion that sites aren't deployed to repositories
  ("causes")

Remote Links:

• GitHub Pull Request #194