I merged changes for [1] to master. Next steps will be updating TC
javadoc to fail on a string "Javadoc Warnings"

[1] https://issues.apache.org/jira/browse/IGNITE-12644

Best regards,
Ivan Pavlukhin

сб, 8 февр. 2020 г. в 21:03, Ivan Pavlukhin <vololo...@gmail.com>:
>
> I created a ticket [1] and PR [2]. Please review.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12644
> [2] https://github.com/apache/ignite/pull/7356
>
> Best regards,
> Ivan Pavlukhin
>
> вт, 4 февр. 2020 г. в 17:51, Ivan Pavlukhin <vololo...@gmail.com>:
> >
> > 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 <vololo...@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.goncha...@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

Reply via email to