[ 
https://issues.apache.org/jira/browse/MWRAPPER-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955114#comment-17955114
 ] 

ASF GitHub Bot commented on MWRAPPER-162:
-----------------------------------------

slawekjaranowski commented on PR #167:
URL: https://github.com/apache/maven-wrapper/pull/167#issuecomment-2921339471

   The commit subject should be also the same as for PR, 
   I will  override by squash




> Broken Link in Maven Wrapper Documentation (404 Error)
> ------------------------------------------------------
>
>                 Key: MWRAPPER-162
>                 URL: https://issues.apache.org/jira/browse/MWRAPPER-162
>             Project: Maven Wrapper
>          Issue Type: Bug
>            Reporter: Montu Sharma
>            Priority: Normal
>         Attachments: image-2025-05-29-13-53-12-417.png, 
> image-2025-05-29-13-53-45-141.png
>
>
> {*}Description{*}:
> I noticed that the Maven Wrapper documentation references a URL that 
> currently returns a 404 error:
>  * {*}Broken Link{*}: [https://www.lewuathe.com/maven-wrapper-home.html]
> This link appears under the "Specifying Maven Distribution Base Path" section.
> {*}Steps to Reproduce{*}:
>  # Visit the Maven Wrapper documentation page (or relevant GitHub README if 
> this applies) - https://maven.apache.org/wrapper/.
>  # Scroll to the section titled “Specifying Maven Distribution Base Path”.
>  # Click on the link {{{}https://www.lewuathe.com/maven-wrapper-home.html{}}}.
>  # It leads to a 404 page.
> {*}Suggested Fix{*}:
> Either remove the dead link or replace it with an alternative source if 
> available. I am also willing to submit a PR to update the documentation 
> accordingly.
> {*}Impact{*}:
> Users referencing the documentation for configuration guidance may be misled 
> or confused by the dead link
> . !image-2025-05-29-13-53-12-417.png|width=207,height=116!
> !image-2025-05-29-13-53-45-141.png|width=214,height=117!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to