gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Renato Javier Marroquín Mogrovejo (JIRA) <j...@apache.org>
Subject [jira] [Commented] (GORA-412) Consider location of @SuppressWarnings("all") in compiled classes
Date Sun, 22 Feb 2015 22:35:11 GMT

    [ https://issues.apache.org/jira/browse/GORA-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332403#comment-14332403
] 

Renato Javier Marroquín Mogrovejo commented on GORA-412:
--------------------------------------------------------

Hi [~lewismc],
I am  +1 for removing the SupressWarnings altogether. I think it is better if users even look
at the warnings if they decide to open such classes in an IDE.

> Consider location of @SuppressWarnings("all") in compiled classes
> -----------------------------------------------------------------
>
>                 Key: GORA-412
>                 URL: https://issues.apache.org/jira/browse/GORA-412
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: gora-compiler
>    Affects Versions: 0.6
>            Reporter: Lewis John McGibbney
>             Fix For: 0.7
>
>
> Right now we silence Javac to any potential warnings by adding the following to compiled
classes
> {code}
> /**
>  * Autogenerated by Avro
>  * 
>  * DO NOT EDIT DIRECTLY
>  */
> package org.apache.gora....;  
> @SuppressWarnings("all")
> ...
> {code}
> This means that the Javadoc associated with the generated class is not interpreted correctly
by clients such as Eclipse.
> I propose to either
>  * remove the SupressWarnings altogether, or
>  * have it generated underneath the Javadoc string.
> Any thoughts folks?



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

Mime
View raw message