[
https://issues.apache.org/jira/browse/EDGENT-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812813#comment-15812813
]
ASF GitHub Bot commented on EDGENT-327:
---------------------------------------
Github user dlaboss commented on a diff in the pull request:
https://github.com/apache/incubator-edgent-website/pull/89#discussion_r95242892
--- Diff: site/_config.yml ---
@@ -126,9 +126,9 @@ host: 127.0.0.1
sourcerepourl: https://github.com/apache/incubator-edgent
downloadsurl: /docs/downloads
projurl: /
-#docsurl: /javadoc/latest
+docsurl: /javadoc/latest
# above yields things like the following when running on a "jekyll serve"
test server
--- End diff --
woops, sorry, just noticed your jira comment that the script is run after
the site is built hence the msgs will still show up when running "jekyll serve"
https://issues.apache.org/jira/browse/EDGENT-327?focusedCommentId=15812317&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15812317
If that's the case maybe add some commentary to README.md (where it
describes running "jekyll serve") so folks know its safe to ignore those
particular error msgs?
> 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)
