[
https://issues.apache.org/jira/browse/QUARKS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405933#comment-15405933
]
Dale LaBossiere commented on QUARKS-205:
----------------------------------------
@cazen vacation was excellent thx!
I think if it's simply renamed to "javadoc", the std "javadoc" task will be
invoked on each subcomponent, and fail when I last tried, and each component
will create its javadoc and then the top level will generate it again. Not
ideal.
After removing the dependency, "default" tasks can be specified in build.gradle
so a simple "gradle" will behave like our "ant" (or "ant all") did. In gradle
terms it looks like "all" => "copyJar aggregateJavadoc" right now (or something
like that :-). The net is that I think we want std gradle tasks to retain
their std behavior. We can add defaults and/or other tasks we we want to
provide "ant all" like behavior too.
> 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)
