Hi,

Mentioned javadoc.css references to some image resources. They present
for 2.3.0 release [1]. But similar url returns 404 for 2.7.0 [2]. Who
knows how to upload resources?

[1] https://ignite.apache.org/releases/2.3.0/javadoc/resources
[2] https://ignite.apache.org/releases/2.7.0/javadoc/resources

пн, 17 дек. 2018 г. в 16:38, Павлухин Иван <vololo...@gmail.com>:

>
> Dmitriy,
>
> Yep, it looks like the problem is inside assembly/docfiles/javadoc.css
>
> I will try to dig into some time later on a spare time. Of course, if
> nobody fixes the problem earlier.
> пн, 17 дек. 2018 г. в 15:18, Dmitriy Pavlov <dpav...@apache.org>:
> >
> > I see the same, browsers checked: Edge & Chrome. I guess it is not a layout
> > is broken, but a style missing.
> >
> > Unfortunately, I don't know how to fix. Probably we should start research
> > from ignite/pom.xml:191
> >
> > <stylesheetfile>${basedir}/assembly/docfiles/javadoc.css</stylesheetfile>
> >
> >
> > пн, 17 дек. 2018 г. в 14:32, Павлухин Иван <vololo...@gmail.com>:
> >
> > > Hi,
> > >
> > > I noticed that Ignite javadoc layout on web for latest versions has
> > > some problems. For example, I see no links near the "Class" at heading
> > > of the page [1]. Here is a screenshot [2]. Do you see the same?
> > >
> > > I was able to build javadoc on my machine. With current configuration
> > > I see the same broken layout. After using commenting out customized
> > > style sheet configuration (referring to assembly/docfiles/javadoc.css)
> > > I was able to obtain an html which renders fine for me.
> > >
> > > Can anyone suggest a simple solution for this?
> > >
> > > [1]
> > > https://ignite.apache.org/releases/2.7.0/javadoc/org/apache/ignite/cache/eviction/EvictionPolicy.html
> > > [2]
> > > https://gist.githubusercontent.com/pavlukhin/c8c7c6266eeab56048c31f5cdfb31d20/raw/1b257ad73f81cb4698f6105a9d1646295ba55795/javadoc_layout.png
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin



--
Best regards,
Ivan Pavlukhin

Reply via email to