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] Resolved: (AVRO-164) Generate paranamer metadata for interfaces as part of SpecificCompiler
Date Wed, 11 Nov 2009 23:54:39 GMT

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

Doug Cutting resolved AVRO-164.
-------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.3.0
         Assignee: Doug Cutting

The fix for this was included in AVRO-185.

> Generate paranamer metadata for interfaces as part of SpecificCompiler
> ----------------------------------------------------------------------
>
>                 Key: AVRO-164
>                 URL: https://issues.apache.org/jira/browse/AVRO-164
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> As discussed a bit in AVRO-146, we shouldn't need to run paranamer in a separate build
step if we have all the schema information already.  We could keep the code paths the same
across the reflected and specific use cases by simply generating the necessary paranamer variable
in SpecificCompiler.

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


Mime
View raw message