commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From britter <...@git.apache.org>
Subject [GitHub] commons-text issue #44: [TEXT-80]: Fixed confusing StrLookup API
Date Thu, 08 Jun 2017 12:02:15 GMT
Github user britter commented on the issue:

    https://github.com/apache/commons-text/pull/44
  
    @chtompki this indicates a source incompatible release. Binary compatible means that you
can swap out the 1.1 jar with the 1.2 jar without a recompile. Would that work?
    
    I can't recall our policy for source incompatible changes. But I think for example adding
new methods to interfaces has been okay in the past. This is also source incompatible (recompilation
fails) but binary compatible (swapping out one jar with another works).


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message