[ https://issues.apache.org/jira/browse/TINKERPOP-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820992#comment-15820992 ]
ASF GitHub Bot commented on TINKERPOP-1443: ------------------------------------------- Github user spmallette commented on the issue: https://github.com/apache/tinkerpop/pull/494 I've set up the branch internal to TinkerPop: https://github.com/apache/tinkerpop/tree/TINKERPOP-1443 @dkuppitz I tried to apply your patch but it still wouldn't build for me. Not sure if I did something wrong. Would you mind applying it yourself and pushing the fix when you get a minute? @metlos Feel free to close this PR at this point. If you have future updates you can submit PRs against that branch (until it's merged). Thanks. > 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 > > 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.4#6332)