[jira] [Updated] (MSHARED-193) API change: let MavenReportRenderer#render() throw an exception

2023-07-06 Thread Michael Osipov (Jira)


 [ 
https://issues.apache.org/jira/browse/MSHARED-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MSHARED-193:
---
Labels:   (was: doxia-2.0.0-stack)

> 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
>Affects Versions: maven-reporting-impl-2.1, maven-reporting-api-3.0
>Reporter: Benson Margulies
>Assignee: Michael Osipov
>Priority: Major
> 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)


[jira] [Updated] (MSHARED-193) API change: let MavenReportRenderer#render() throw an exception

2023-07-04 Thread Michael Osipov (Jira)


 [ 
https://issues.apache.org/jira/browse/MSHARED-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MSHARED-193:
---
Component/s: (was: maven-reporting-impl)

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


[jira] [Updated] (MSHARED-193) API change: let MavenReportRenderer#render() throw an exception

2023-07-01 Thread Michael Osipov (Jira)


 [ 
https://issues.apache.org/jira/browse/MSHARED-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov updated MSHARED-193:
---
Summary: API change: let MavenReportRenderer#render() throw an exception  
(was: No checked exceptions for rendering)

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