Mailing-List: contact dev-help@quarks.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@quarks.incubator.apache.org
Date: Tue, 2 Aug 2016 20:00:21 +0000 (UTC)
From: "Dale LaBossiere (JIRA)" <jira@apache.org>
To: dev@quarks.incubator.apache.org
Message-ID: <JIRA.12978006.1465781290000.203515.1470168021958@Atlassian.JIRA>
In-Reply-To: <JIRA.12978006.1465781290000@Atlassian.JIRA>
References: <JIRA.12978006.1465781290000@Atlassian.JIRA> <JIRA.12978006.1465781290884@arcas>
Subject: [jira] [Commented] (QUARKS-205) Create gradle Javadoc task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 Aug 2016 20:00:25 -0000


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

Dale LaBossiere commented on QUARKS-205:
----------------------------------------

I discovered that some doc links were broken due to "doc-files" files not getting copied to the javadoc target.  I'm fixing that with PR-178.

At a high level, I came to realize that the normal gradle "javadoc" task is not being used to generate the javadoc.  Instead, this top level "aggregateJavadoc" task is what's used to generate everything.  Also, this "aggregateJavadoc" task is a dependency of the top level "build" task.   This doesn't seem like a configuration that a gradle user would expect.  Seems like something we might want to cleanup up eventually?

> Create gradle Javadoc task
> --------------------------
>
>                 Key: QUARKS-205
>                 URL: https://issues.apache.org/jira/browse/QUARKS-205
>             Project: Quarks
>          Issue Type: Task
>            Reporter: Cazen Lee
>            Assignee: Cazen Lee
>            Priority: Minor
>              Labels: build, newbie
>
> Javadoc parity with ant javadoc task


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)