accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1487) Package javadocs for monitor better, or not at all
Date Tue, 08 Apr 2014 03:03:17 GMT


ASF subversion and git services commented on ACCUMULO-1487:

Commit 479a36bd991e831fba04118c51a605a601a86dec in accumulo's branch refs/heads/ACCUMULO-378
from [~ctubbsii]
[;h=479a36b ]

ACCUMULO-1487 Fix build command in convenience script

> Package javadocs for monitor better, or not at all
> --------------------------------------------------
>                 Key: ACCUMULO-1487
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: docs
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>              Labels: Documentation
>             Fix For: 1.6.0
> Packaging javadocs are problematic for the monitor page because we need to do something
> {code}mvn clean compile javadoc:aggregate package{code}
> so the classes are compiled prior to building the javadocs (for some reason, this is
a requirement), and the javadocs are available to be packaged when the monitor is packaged.
However, this essentially duplicates the build lifecycle between the initialize and compile
> Options:
> # Use maven-invoker-plugin to execute the "mvn compile javadoc:aggregate" separately,
with minimal plugins configured (not sure the effect this will have on maven-release-plugin
which also executes maven-invoker-plugin).
> # Make monitor depend on javadoc artifacts from other modules, and serve them (repackaging,
if necessary). This might require javadoc artifacts to be built whenever the monitor is built,
and not just during a release.
> # My preferred option: don't package javadocs with the monitor. Instead, link to the
Accumulo website (with a configurable base address, to support environments where javadocs
are mirrored, in case they can't directly access the Apache website).

This message was sent by Atlassian JIRA

View raw message