[
https://issues.apache.org/jira/browse/AVRO-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113234#comment-17113234
]
Hudson commented on AVRO-2572:
------------------------------
SUCCESS: Integrated in Jenkins build AvroJava #880 (See
[https://builds.apache.org/job/AvroJava/880/])
[AVRO-2572] Fixup the soname slightly to not have the extra .0 at the (dkulp:
[https://github.com/apache/avro/commit/833127d6ed09618babd1cce10053d5f183740dab])
* (edit) lang/c++/CMakeLists.txt
> [avrocpp] Too restrictive SONAME
> --------------------------------
>
> Key: AVRO-2572
> URL: https://issues.apache.org/jira/browse/AVRO-2572
> Project: Apache Avro
> Issue Type: Bug
> Components: c++
> Affects Versions: 1.8.1, 1.9.0, 1.8.2, 1.9.1
> Reporter: Laurent Stacul
> Priority: Major
>
> Hello,
> While I was upgrading Apache Avro from 1.8.2 to 1.9.1, I checked the binary
> compatibility using RedHat libabigail. If the code was OK which is what I
> expected from the Semantic Versioning of the project, I did not expect that
> the binary compatibility check failed due to the soname.
> I checked and found out this point was raised for the C component and fixed
> there: [https://github.com/apache/avro/pull/239.]
> If the binary compatibility is respected across the major versions of
> libavrocpp, I would expect
> {code:java}
> SONAME Library soname: [libavrocpp.so.1]{code}
> instead of:
> {code:java}
> SONAME Library soname: [libavrocpp.so.1.10.0-SNAPSHOT.0]{code}
> Do you agree on this ?
> Regards,
> Laurent
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
