commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (EMAIL-169) MimeMessageUtils.writeMimeMessage writes stacktrace
Date Thu, 16 Mar 2017 21:10:41 GMT

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

Sebb resolved EMAIL-169.
------------------------
       Resolution: Fixed
    Fix Version/s: 1.5

URL: http://svn.apache.org/viewvc?rev=1787246&view=rev
Log:
EMAIL-169 MimeMessageUtils.writeMimeMessage writes stacktrace

Modified:
    commons/proper/email/trunk/src/changes/changes.xml
    commons/proper/email/trunk/src/main/java/org/apache/commons/mail/util/MimeMessageUtils.java



> MimeMessageUtils.writeMimeMessage writes stacktrace
> ---------------------------------------------------
>
>                 Key: EMAIL-169
>                 URL: https://issues.apache.org/jira/browse/EMAIL-169
>             Project: Commons Email
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 1.5
>
>
> The MimeMessageUtils.writeMimeMessage method displays a stack trace if there has been
a problem writing to the output file and the file cannot subsequently be closed. It also catches
Exception rather than IOE.
> Library code should almost never display stack traces.
> The other methods in the class allow the close failure to be propagated.
> This should too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message