You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@opennlp.apache.org by "Daniel Naber (JIRA)" <ji...@apache.org> on 2012/07/19 23:39:34 UTC

[jira] [Reopened] (OPENNLP-525) Exception cleanup in opennlp-tools

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

Daniel Naber reopened OPENNLP-525:
----------------------------------


Thanks for committing, I'm attaching a suggestion on how the causing exception can be kept for IOException without losing Java 1.5 compatibility. Not really tested as I don't have Java 1.5 here. (Thus reopening, let me know if that's not the workflow you prefer)
                
> Exception cleanup in opennlp-tools
> ----------------------------------
>
>                 Key: OPENNLP-525
>                 URL: https://issues.apache.org/jira/browse/OPENNLP-525
>             Project: OpenNLP
>          Issue Type: Improvement
>            Reporter: Daniel Naber
>            Assignee: Aliaksandr Autayeu
>            Priority: Minor
>             Fix For: tools-1.5.3
>
>         Attachments: opennlp-java15.patch, opennlp_exception_cleanup.patch
>
>
> As a follow-up to OPENNLP-522 I looked through the exceptions throw in opennlp-tools and tried to improve them, i.e. adding better error messages and not losing the causing exception. I must admit I'm not sure if it's really needed to show the cause in CLI.java or if that always happens anyway (as there are e.printStackTrace() statements in the code). The patch also contains one or two small typo fixes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira