You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthias Bünger (Jira)" <ji...@apache.org> on 2024/06/05 14:45:00 UTC
[jira] [Updated] (MSITE-1010) site-deployment for POM projects does not create project folders in site-repository
[ https://issues.apache.org/jira/browse/MSITE-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Bünger updated MSITE-1010:
-----------------------------------
Description:
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
{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}
was:
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
{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:
/ (root of site-repository)
/css
/project-A
/project-B
/project-C
report.html
{code}
> site-deployment for POM projects does not create project folders 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
>
> 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
> {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)