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 Wed, 18 May 2016 09:29:13 GMT

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

ASF GitHub Bot commented on QUARKS-48:
--------------------------------------

Github user Cazen commented on the pull request:

    https://github.com/apache/incubator-quarks-website/pull/62#issuecomment-219973453
  
    Your encourage is great motivation to me. Thank you @dlaboss 
    
    I think your idea that prohibit the direct using is good. Could we discuss in another
jira issue? It will be affected a lot of impact on the project(can be done with replace script
but it modify a lot of files). I think it is better to handle one task at a one Jira issue
for good traceability. 
    
    -- Done in this PR
    - Create lastest&0.4.0 JavaDoc
    - Using property(docsurl) to URLs instead of hardcoding
    
    -- Will be held in another PR
    - Apply a select box in JavaDoc for seperate version info where exist in topnav&header.
    - Replace from all the URLs that hardcoded to using properties(e.g community.md)
    - Prohibits the direct use of Quarks and quarks, and let them to use the properties


> 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
(v6.3.4#6332)

Mime
View raw message