[MNG-7888] maven releases do not resolve URL in pom
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Henning Schmiedehausen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=henning)** opened **[MNG-7888](https://issues.apache.org/jira/browse/MNG-7888?redirect=false)** and commented
The released poms contain `https://github.com/apache/maven-javadoc-plugin/tree/${project.scm.tag}`. 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.
---
No further details from [MNG-7888](https://issues.apache.org/jira/browse/MNG-7888?redirect=false)
Contributor guide
Research direction
No repository file, test, or entry point is named. Start by locating the Maven parent POM and the release configuration that produces the published POM, then compare it with the maven-javadoc-plugin 3.4.1 artifact cited in the issue. Done means released POM URLs no longer contain the ${project.scm.tag} placeholder for tools that do not resolve it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100