[
https://issues.apache.org/jira/browse/MSHARED-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739333#comment-17739333
]
Tamas Cservenak commented on MSHARED-193:
-----------------------------------------
And what will user (or whatever layer) do with this checked exception? Can it
act on it, or just log and fail? Also, this issue is from 2011, so java5? When
there was no runtime ioex existed.
> API change: let MavenReportRenderer#render() throw an exception
> ---------------------------------------------------------------
>
> Key: MSHARED-193
> URL: https://issues.apache.org/jira/browse/MSHARED-193
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-reporting-api, maven-reporting-impl
> Affects Versions: maven-reporting-impl-2.1, maven-reporting-api-3.0
> Reporter: Benson Margulies
> Assignee: Michael Osipov
> Priority: Major
> Labels: doxia-2.0.0-stack
> Fix For: maven-reporting-api-4.0.0-M7
>
>
> It seems unfortunate that
> [org.apache.maven.reporting.MavenReportRenderer.render()|https://maven.apache.org/shared/maven-reporting-api/apidocs/org/apache/maven/reporting/MavenReportRenderer.html]
> does not throw MavenReportingException. Thus, even though the execute method
> for a report throws that exception, rendering problems cannot.
> Obviously, a change to this would ramify. Would there be any chance of
> acceptance for a patch that added this 'throws'? Alternatively, how about an
> unchecked cousin of MavenReportingException?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
