Ivan,
Good catch.
1. Let's remove this label at all. Neither Spark [1] nor Cassandra [2] has
it and their docs look much better.
2. Agree, time to change the year in the copyright.
3. Still, something is wrong with our font size. Just compare to [1] and
[2] to see the difference. Can we reuse
I went through a couple of pages and layout looks good.
A couple of aside notes:
1. There is a label "Ignite - In-Memory Database and Caching
Platform". Do we need that label at all? Can we replace it with a link
having text "Ignite" and referring to ignite.apache.org?
2. The copyright is out of
+ Sergey
-
Denis
On Tue, Jun 11, 2019 at 9:21 AM Denis Magda wrote:
> Sergey,
>
> Could you please chime in? I do believe we have special tests to ensure
> the javadoc is not broken. Visually, everything looks good. But I'll
> encourage others to double check.
>
> -
> Denis
>
>
> On Tue, Jun
Sergey,
Could you please chime in? I do believe we have special tests to ensure the
javadoc is not broken. Visually, everything looks good. But I'll encourage
others to double check.
-
Denis
On Tue, Jun 11, 2019 at 7:04 AM Dmitriy Pavlov wrote:
> Igniters, Ivan,
>
> could you please verify
Igniters, Ivan,
could you please verify new release JavaDoc doesn't have same problems:
https://ignite.apache.org/releases/2.7.5/javadoc/
Sincerely,
Dmitriy Pavlov
чт, 31 янв. 2019 г. в 21:30, Dmitriy Pavlov :
> Sure, I don't see any issues with using the default style. It is
> definitely
Sure, I don't see any issues with using the default style. It is
definitely better than broken CSS.
Thank you for accurate & detailed research.
If nobody minds I could apply a patch with a switch to defaults.
чт, 31 янв. 2019 г. в 11:11, Павлухин Иван :
> Hi,
>
> Continuation of the story. I
Hi,
Continuation of the story. I build javadocs locally and checked how it
renders with manually added images. Unfortunately there are several
visible artifacts. I guess the reason here is that stylesheet and
images was suitable for an older version of javadoc maven plugin but
not for a newer
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]
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 :
>
> I see the same, browsers checked: Edge & Chrome. I guess it is
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
${basedir}/assembly/docfiles/javadoc.css
пн, 17 дек. 2018 г. в 14:32, Павлухин Иван :
>
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
11 matches
Mail list logo
