[
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802747#comment-15802747
]
Queenie Ma commented on EDGENT-327:
-----------------------------------
I looked into the {{ERROR `/javadoc/latest/resources/fonts/dejavu.css' not
found}} messages. It seems to be a bug in the Javadoc tool due to a dangling
reference to dejavu.css in stylesheet.css. Note the {{@import}} statement
below.
{code:title=stylesheet.css|borderStyle=solid}
@import url('resources/fonts/dejavu.css');
body {
background-color:#ffffff;
color:#353833;
font-family:'DejaVu Sans', Arial, Helvetica, sans-serif;
font-size:14px;
margin:0;
}
...
{code}
Found this related issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=470739.
A person who commented on that issue submitted a Java bug, but it seems that
the bug hasn't been fixed.
Workarounds are:
# Manually add the dejavu.css font file to the generated Javadoc (not sure
where to get that file)
# Remove the {{@import}} statement and use a different default font
Thoughts?
> some http urls in the website prevent full local testing
> --------------------------------------------------------
>
> Key: EDGENT-327
> URL: https://issues.apache.org/jira/browse/EDGENT-327
> Project: Edgent
> Issue Type: Task
> Components: Web Site
> Reporter: Dale LaBossiere
> Assignee: Queenie Ma
> Priority: Trivial
>
> If you create a local / test instance of the website (e.g., "jekyll server")
> all of the javadoc related links go to the live website.
> site/_config.yml defines docurl which is used in many places. See the note
> there about issues encountered when I tried changing it from a http url to a
> / url... though overall it seemed to work.
> Also the javadoc "latest", 1.0.0, ... links in
> site/_data/mydoc/mydoc_topnav.yml are http links.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
