[ 
https://issues.apache.org/jira/browse/AVRO-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Doug Cutting updated AVRO-1550:
-------------------------------

    Fix Version/s: 1.8.0
         Assignee: Thomas Friedrich
           Status: Patch Available  (was: Open)

This pom change might be considered incompatible.  If a project doesn't specify 
an explicit version of Protobuf, but inherits Avro's version, then this change 
will cause the project to upgrade to 2.5, which might break it.  So we should 
probably target this for Avro 1.8 (which permits such incompatibilities).

Also, I think the 1.7.x avro-protobuf jars work with Protobuf 2.5, since they 
contain no generated code and only call public Protobuf APIs that haven't 
incompatibly changed, so a project that explicitly depends on Protobuf 2.5 will 
currently work with avro-protobuf, no?  So I don't think this change is urgent.

> Move protobuf dependency to 2.5.0
> ---------------------------------
>
>                 Key: AVRO-1550
>                 URL: https://issues.apache.org/jira/browse/AVRO-1550
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.6
>            Reporter: Thomas Friedrich
>            Assignee: Thomas Friedrich
>            Priority: Minor
>             Fix For: 1.8.0
>
>         Attachments: AVRO-1550.patch
>
>
> Protobuf dependency in java module should be moved up to current version 
> 2.5.0 from 2.4.1.
> Need to regenerate Java source for Test class under org.apache.avro.protobuf 
> with new protobuf version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to