Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27D0ECAA6 for ; Mon, 3 Jun 2013 16:55:23 +0000 (UTC) Received: (qmail 27706 invoked by uid 500); 3 Jun 2013 16:55:22 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 26821 invoked by uid 500); 3 Jun 2013 16:55:21 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 26480 invoked by uid 99); 3 Jun 2013 16:55:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jun 2013 16:55:20 +0000 Date: Mon, 3 Jun 2013 16:55:20 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1487) Package javadocs for monitor better, or not at all MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673310#comment-13673310 ] Christopher Tubbs commented on ACCUMULO-1487: --------------------------------------------- {quote}would that simplify any of the options?{quote} That's part of ACCUMULO-210, and I plan on doing that anyway. It doesn't simplify anything, but it is a prerequisite for Option 2. > Package javadocs for monitor better, or not at all > -------------------------------------------------- > > Key: ACCUMULO-1487 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1487 > Project: Accumulo > Issue Type: Improvement > Reporter: Christopher Tubbs > Fix For: 1.6.0 > > > Packaging javadocs are problematic for the monitor page because we need to do something like: > {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 phase. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira