You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2016/09/12 11:49:20 UTC

[jira] [Commented] (TINKERPOP-1443) Use an API checker during build

    [ https://issues.apache.org/jira/browse/TINKERPOP-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483904#comment-15483904 ] 

stephen mallette commented on TINKERPOP-1443:
---------------------------------------------

We should have documented that change in our upgrade docs (the upgrade docs were pretty slack on this release). For various reasons, we don't adhere strictly to semantic versioning, but do attempt to not introduce "major" breaking changes in patch release and certainly not without some entry in the upgrade documentation. The API checker looks interesting - I will look into that - thanks for the link.

> 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)