[
https://issues.apache.org/jira/browse/TINKERPOP-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868542#comment-15868542
]
ASF GitHub Bot commented on TINKERPOP-1443:
-------------------------------------------
Github user metlos commented on the issue:
https://github.com/apache/tinkerpop/pull/494
@spmallette this is because right now, revapi is configured to allow
breaking changes on minor version increase. The branch builds a 3.3.0-SNAPSHOT
and is compared against the latest release - 3.2.4. That means that revapi
basically allows any change to go through.
If in the root pom, you change the config to only allow
`potentiallyBreaking` changes on minor version increase, you will see quite a
list of breakages ;)
> Use an API checker during build
> -------------------------------
>
> Key: TINKERPOP-1443
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1443
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.2.2
> Reporter: Lukas Krejci
> Assignee: stephen mallette
>
> Tinkerpop 3.2.2 changed the signature of the method
> {{GraphTraversal.hasLabel}} from {{(String...)}} to {{(String, String...)}}.
> While this is certainly an improvement, it is both source and binary
> incompatible change.
> I.e. even if every usage of {{hasLabel}} had at least one parameter in the
> user code, none of those calls will work until all the user code is
> recompiled using Tinkerpop 3.2.2.
> I don't know the versioning policy of Tinkerpop but changes like the above in
> a micro/patch release are generally unexpected.
> Please consider API checkers like http://revapi.org to warn about such
> incompatible API changes...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
