[ https://issues.apache.org/jira/browse/TINKERPOP-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962942#comment-15962942 ]
ASF GitHub Bot commented on TINKERPOP-1443: ------------------------------------------- Github user spmallette commented on a diff in the pull request: https://github.com/apache/tinkerpop/pull/596#discussion_r110668972 --- Diff: .travis.yml --- @@ -5,6 +5,18 @@ jdk: - oraclejdk8 sudo: required dist: trusty +cache: + directories: + - $HOME/mvn-home + +install: + # install maven 3.3.9 if it is not in cache already --- End diff -- I'm not sure I see why it matters. The requirement is at least 3.2.5 and 3.3.9 meets that requirement. I suppose we could pin travis to the minimum version but is there any particular reason to do so? > 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)