avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-185) specific should not depend on reflect
Date Wed, 11 Nov 2009 22:50:39 GMT

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

Doug Cutting updated AVRO-185:

    Attachment: AVRO-185.patch

Here's a new version of the patch that
 -  fixes the javadoc
 -  moves reflection back to reflect
 -  removes paranamer from code generator in build.xml
Existing tests use reflection on generated test classes.  Perhaps that ought to be changed,
but until it is, we still run paranamer on generated test code to permit this.

> specific should not depend on reflect
> -------------------------------------
>                 Key: AVRO-185
>                 URL: https://issues.apache.org/jira/browse/AVRO-185
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>         Attachments: AVRO-185.patch, AVRO-185.patch
> Currently the specific implementation inherits from the reflect implementation.  To fix
AVRO-80, this dependency should be reversed, since specific will still share all data representations
but records and enums with generic, but specific and reflect will no longer use common representations
for strings and arrays.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message