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

Michael Osipov commented on MSHARED-193:
----------------------------------------

How likely is this? I mean if you need to stream the data to process it, then 
how to visualize so much data in a report? Does this then make sense?

> 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
>
> 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)

Reply via email to