edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-48) Generate JavaDoc for website
Date Tue, 17 May 2016 13:00:15 GMT

    [ https://issues.apache.org/jira/browse/QUARKS-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286564#comment-15286564

ASF GitHub Bot commented on QUARKS-48:

Github user dlaboss commented on a diff in the pull request:

    --- Diff: site/_includes/header.html ---
    @@ -98,7 +98,7 @@
                           <a href="#" class="dropdown-toggle" data-toggle="dropdown" role="button"
aria-haspopup="true" aria-expanded="false">Documentation</a>
                           <ul class="dropdown-menu">
                             <li><a href="docs/home">Documentation Home</a></li>
    -                        <li><a href="{{ site.projurl }}/docs/javadoc/index.html">Javadoc</a></li>
    --- End diff --
    The original used `{{ site.projurl }}` to provide a level of indirection.  That seems
generally good and particularly desirable since the url will change once again when the project
name is changed.  Can such a scheme be applied everywhere - at least for non-autogenerated
javadoc files?  Related question: can something similar  be done for the project name - e.g.,
something like `site.projname` instead of using `Quarks` directly?

> Generate JavaDoc for website
> ----------------------------
>                 Key: QUARKS-48
>                 URL: https://issues.apache.org/jira/browse/QUARKS-48
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Cazen Lee
> I'm not sure but it seems that Javadoc branch does not exist.
> I think we can make JavaDoc branch like below:
> https://github.com/quarks-edge/quarks/tree/gh-pages

This message was sent by Atlassian JIRA

View raw message