[
https://issues.apache.org/jira/browse/TINKERPOP3-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP3-944:
----------------------------------------
Fix Version/s: 3.2.0-incubating
> Consider deprecating or better enforcing Graph.Exceptions.elementNotFound
> -------------------------------------------------------------------------
>
> Key: TINKERPOP3-944
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-944
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Labels: breaking
> Fix For: 3.2.0-incubating
>
>
> As it sits right now, the standard {{elementNotFound}} exception is not used
> in the core code base, but we are validating that it is being thrown in the
> test suite by providers! The test is actually faulty because it is not
> asserting the message and just that it is a {{NoSuchElementException}} which
> is causing the problem. We should either deprecate this method and just
> validate {{NoSuchElementException}} or use it in full and force providers to
> do the same.
> This has the potential to be a breaking change as it might break tests if
> providers aren't using that standard exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
