Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/494
> the `ImmutablePath` method changes are internal changes
I think that's the point. It would have been an internal change if the
methods were internal, but they're public. We can assume that people never used
it directly, but we won't know. Maybe someone out there added a TinkerPop
dependency in his project, because he liked the `ImmutablePath` implementation,
but nothing else (you know, like "let's add Apache Commons, they have a nice
method in `StringUtils`").
Hence, if we need to touch public method in a public class: deprecate them
and remove/change them in the next major release.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
