[
https://issues.apache.org/jira/browse/RAT-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578308#comment-17578308
]
Michael Osipov commented on RAT-309:
------------------------------------
[~pottlinger], sure. It all started with my short sight in MSHARED-1024. I
cleaned up too much which I did not know back then. You saw it in RAT-300. Then
I was made aware of
https://github.com/apache/maven-reporting-api/pull/2#issuecomment-1198787432. I
started to investigate and he is right. I broke API. In parallel MPIR-423 was
reported which depicted that m-r-impl was broken for a long time but never
noticed. Therefore, I restored m-r-api and fixed m-r-impl. Now I started a
trail of fix releases with all of our reporting plugins. Some plugins don't use
m-r-impl as MJAVADOC because of inheritance, just like RAT plugin. So truly my
fault with RAT-300 and RAT-309. If I would have done MSHARED-1024 right it
would have never happened, but at least MPIR-423 showed me that stuff is flawed.
> Upgrade Maven Reporting API to 3.1.1/Complete with Maven Reporting Impl 3.2.0
> -----------------------------------------------------------------------------
>
> Key: RAT-309
> URL: https://issues.apache.org/jira/browse/RAT-309
> Project: Apache Rat
> Issue Type: Bug
> Affects Versions: 0.14
> Reporter: Michael Osipov
> Assignee: Philipp Ottlinger
> Priority: Major
> Fix For: 0.15
>
>
> This is basically a copy of MJAVADOC-723.
> It was discovered in RAT while verifying RAT-200 after 0.14 was released.
> [~michael-o] can you provide a bit more context? Does the problem have
> security implications apart from breaking the generation of maven-sites?
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
