[
https://issues.apache.org/jira/browse/ARROW-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403549#comment-16403549
]
Renato Javier Marroquín Mogrovejo commented on ARROW-2310:
----------------------------------------------------------
sure, I can try clean the javadocs. However, adding "generated" java comments
for methods doesn't really mean that will help people understanding the code
better. This will just help us in not getting the warnings anymore. I guess
that is ok for now, and update javadocs "on demand", right?
Also I started giving this a look and got this:
arrow/java/format/target/generated-sources/flatc/org/apache/arrow/flatbuf/Block.java:17:
warning: no @return
[ERROR] public long offset() \{ return bb.getLong(bb_pos + 0); }
This code is generated from the format module. Should we just ignore javadoc
linting on this module?
> Source release scripts fail with Java8
> --------------------------------------
>
> Key: ARROW-2310
> URL: https://issues.apache.org/jira/browse/ARROW-2310
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.10.0
>
>
> It's getting harder and harder to install Java7 these days. On a new install
> of Ubuntu 16.04 I am not even sure how to get Oracle's Java7 installed
> (though Java8 can be installed through a PPA).
> In lieu of fixing all the javadoc problems, it would be great if there was
> some other workaround to build the release on Java8
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
