[
https://issues.apache.org/jira/browse/MPMD-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930201#comment-17930201
]
ASF GitHub Bot commented on MPMD-407:
-------------------------------------
knoobie commented on PR #175:
URL: https://github.com/apache/maven-pmd-plugin/pull/175#issuecomment-2681249472
@michael-o Sorry for the ping.. I wasn't really sure where to post this,
especially without a proper reproducer..
We noticed some interesting / weird behavior since this change in our
internal builds - once maven-pmd-plugin 3.26.0 is in use (containing DOXIA 2.0
GA) we got problem building against an internal JFrog Artifactory where it does
not return proper 404 "errors" for "missing" site.xml (instead 401) resulting
in a complete build crash.
Example:
```java
An error has occurred in PMD report generation. The site descriptor cannot
be resolved from the repository:
Unable to locate site descriptor: The following artifacts could not be
resolved: internal:parent-pom:xml:site:version (absent):
Could not transfer artifact internal:parent-pom:xml:site:version from/to
repo (https://internal-jfrog-instance/artifactory/repos): status code: 401,
reason phrase: (401) -> [Help 1]
```
> Upgrade to Doxia 2.0.0 GA Stack
> -------------------------------
>
> Key: MPMD-407
> URL: https://issues.apache.org/jira/browse/MPMD-407
> Project: Maven PMD Plugin
> Issue Type: Dependency upgrade
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.26.0
>
>
> * Upgrade to Doxia 2.0.0
> * Upgrade to Maven Reporting Impl 4.0.0
> * Upgade to Maven JXR 3.5.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
