You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Gilles (JIRA)" <ji...@apache.org> on 2018/09/17 11:02:00 UTC

[jira] [Commented] (GEOMETRY-16) Reassess Classes in Exception API

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

Gilles commented on GEOMETRY-16:
--------------------------------

Link added to GEOMETRY-8 issue because I think that my comment there is still valid.

> Reassess Classes in Exception API
> ---------------------------------
>
>                 Key: GEOMETRY-16
>                 URL: https://issues.apache.org/jira/browse/GEOMETRY-16
>             Project: Apache Commons Geometry
>          Issue Type: Task
>            Reporter: Matt Juntunen
>            Priority: Major
>
> Before releasing v1.0 of this project, we should reassess the exception types that are included in the public API to ensure that each class is actually worth including on its own. The overall goal is to keep the exception hierarchy useful but with the smallest possible footprint.
> Some examples of existing types that could be combined are the CardanSingularityException and EulerSingularityException in the Rotation class. It is very unlikely that differentiating between these two types of singularities will be important to users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)