[
https://issues.apache.org/jira/browse/MSHARED-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17739331#comment-17739331
]
Herve Boutemy commented on MSHARED-193:
---------------------------------------
adding a checked exception does not cost anything, lets flexibility for users
refusing just force them to tweak when they need it: I don't see why
> No checked exceptions for rendering
> -----------------------------------
>
> 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
> Priority: Major
> Labels: doxia-2.0.0-stack
> Fix For: waiting-for-feedback
>
>
> 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)
