[
https://issues.apache.org/jira/browse/MNG-7888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766034#comment-17766034
]
Henning Schmiedehausen commented on MNG-7888:
---------------------------------------------
then what is the point of having metadata such as doc urls, issue tracker etc.
if they can't be read outside a maven context? We could pretend that the maven
universe is hermetic and only the maven driven tooling exists (e.g. site
generation).
The real world looks different. Case in point are the URIs above. Most projects
get this right (they fully resolve the pom before publishing).
> maven releases do not resolve URL in pom
> -----------------------------------------
>
> Key: MNG-7888
> URL: https://issues.apache.org/jira/browse/MNG-7888
> Project: Maven
> Issue Type: Bug
> Reporter: Henning Schmiedehausen
> Priority: Major
>
> The released poms contain
> {{<url>https://github.com/apache/maven-javadoc-plugin/tree/${project.scm.tag}</url>}}.
> As a result, tools that do not actively parse and resolve the pom can't
> display a valid URL but only show a link with the placeholder.
> E.g.
> https://search.maven.org/artifact/org.apache.maven.plugins/maven-javadoc-plugin/3.4.1/maven-plugin
> This seems to be a fundamental problem with the maven parent pom.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
