You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Tom White (JIRA)" <ji...@apache.org> on 2015/06/26 16:43:05 UTC

[jira] [Resolved] (AVRO-1681) Improve generated JavaDocs

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

Tom White resolved AVRO-1681.
-----------------------------
       Resolution: Fixed
         Assignee: Charles Gariépy-Ikeson
     Hadoop Flags: Reviewed
    Fix Version/s: 1.8.0

I committed this. Thanks Charles!

> Improve generated JavaDocs
> --------------------------
>
>                 Key: AVRO-1681
>                 URL: https://issues.apache.org/jira/browse/AVRO-1681
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>    Affects Versions: 1.7.7
>            Reporter: Charles Gariépy-Ikeson
>            Assignee: Charles Gariépy-Ikeson
>            Priority: Minor
>             Fix For: 1.7.8, 1.8.0
>
>         Attachments: AVRO-1681-TRUNK.patch, AVRO-1681.patch
>
>
> Hi everyone!
> I've noticed that the JavaDocs generated by the SpecificCompiler could use a little TLC. Our usage of Avro includes the IPC component, and it would be nice if the JavaDocs that were generated from our avpr files were a little more verbose, especially when working with IDEs that integrate JavaDocs from the classes we are using. It would help usage of the interfaces and classes generated from the protocol file, without having to dive deeper into the class or protocol file from which it was generated.
> I've made a first attempt at accomplishing this. This is my first patch, so don't hesitate to point out something I've missed or needs improving.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)