ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Pavlukhin <vololo...@gmail.com>
Subject Re: JAVADOC fails on local build. Should it be checked on TC?
Date Tue, 04 Feb 2020 14:51:57 GMT
The next bit I found out is that links like
"<link>https://hadoop.apache.org/docs/current/api/</link>"
are needed to have working links to external classes in javadocs (e.g.
Hadoop ones). Unfortunately, we are not consistent with external
links. E.g. references to JCache classes are rendered as plain text in
our javadocs [1].

For now I suggest to drop Hadoop links from maven plugin configuration
as well. If there are no objections I will prepare a PR.

[1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/CacheEntryProcessor.html

вт, 4 февр. 2020 г. в 15:04, Ivan Pavlukhin <vololo100@gmail.com>:
>
> Alexey,
>
> Thank you for the hint. Actually my bet was the same. But currently I
> have no understanding how
> "<link>https://hadoop.apache.org/docs/current/api/</link>" tag is used
> and is it used at all.
>
> вт, 4 февр. 2020 г. в 15:01, Alexey Goncharuk <alexey.goncharuk@gmail.com>:
> >
> > Ivan,
> >
> > My guess would be that the link was included for the Hadoop Accelerator
> > which we all agreed to remove [1]. I think it is safe to remove it from
> > pom.xml completely.
> >
> > [1]
> > http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html
>
>
>
> --
> Best regards,
> Ivan Pavlukhin



-- 
Best regards,
Ivan Pavlukhin

Mime
View raw message