You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2025/02/04 18:09:00 UTC
[jira] [Updated] (MSITE-1032) AbstractDeployMojo.getDeployModuleDirectory() does not work for Git SCM URLs
[ https://issues.apache.org/jira/browse/MSITE-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated MSITE-1032:
-----------------------------------
Description:
A git scm URL looks like this {{scm:git:git@github.com:codehaus-plexus/plexus-sec-dispatcher.git}}, however the module directory derived from this URL is totally off in https://github.com/apache/maven-site-plugin/blob/5a0e56d30c716821f922b9ee0981cda28284578f/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java#L217 (when the topSiteURL, in https://maven.apache.org/plugins/maven-site-plugin/stage-mojo.html#topSiteURL, isn't set).
The underlying logic is not quite clear to me as according to https://maven.apache.org/pom.html#Site_Distribution is
{quote}
...responsible for defining how to deploy the project's site and documentation
{quote}
This is usually fundamentally different from the URL which is used by end users to access the documentation (which is rather given by {{project->url}}). Why was distributionManagament used as the default source for calculating links?
was:
A git scm URL looks like this {{scm:git:git@github.com:codehaus-plexus/plexus-sec-dispatcher.git}}, however the module directory derived from this URL is totally off in https://github.com/apache/maven-site-plugin/blob/5a0e56d30c716821f922b9ee0981cda28284578f/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java#L217 (when the topSiteURL, in https://maven.apache.org/plugins/maven-site-plugin/stage-mojo.html#topSiteURL, isn't set).
The underlying logic is not quite clear to me as according to https://maven.apache.org/pom.html#Site_Distribution the site URL is just
{quote}
distributionManagement is responsible for defining how to deploy the project's site and documentation
{quote}
This is usually fundamentally different from the URL which is used by end users to access the documentation (which is rather given by {{project->url}}). Why was distributionManagament used as the default source for calculating links?
> AbstractDeployMojo.getDeployModuleDirectory() does not work for Git SCM URLs
> ----------------------------------------------------------------------------
>
> Key: MSITE-1032
> URL: https://issues.apache.org/jira/browse/MSITE-1032
> Project: Maven Site Plugin
> Issue Type: Improvement
> Components: site:stage(-deploy)
> Reporter: Konrad Windszus
> Priority: Major
>
> A git scm URL looks like this {{scm:git:git@github.com:codehaus-plexus/plexus-sec-dispatcher.git}}, however the module directory derived from this URL is totally off in https://github.com/apache/maven-site-plugin/blob/5a0e56d30c716821f922b9ee0981cda28284578f/src/main/java/org/apache/maven/plugins/site/deploy/AbstractDeployMojo.java#L217 (when the topSiteURL, in https://maven.apache.org/plugins/maven-site-plugin/stage-mojo.html#topSiteURL, isn't set).
> The underlying logic is not quite clear to me as according to https://maven.apache.org/pom.html#Site_Distribution is
> {quote}
> ...responsible for defining how to deploy the project's site and documentation
> {quote}
> This is usually fundamentally different from the URL which is used by end users to access the documentation (which is rather given by {{project->url}}). Why was distributionManagament used as the default source for calculating links?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)