Mailing-List: contact chukwa-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@hadoop.apache.org
Message-ID: <1975903409.1244830447588.JavaMail.jira@brutus>
Date: Fri, 12 Jun 2009 11:14:07 -0700 (PDT)
From: "Ari Rabkin (JIRA)" <jira@apache.org>
To: chukwa-dev@hadoop.apache.org
Subject: [jira] Commented: (CHUKWA-288) Cleaner build management for
 chukwa-pig.jar
In-Reply-To: <1556609716.1244828527393.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CHUKWA-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718927#action_12718927 ] 

Ari Rabkin commented on CHUKWA-288:
-----------------------------------

+1 to having ant make Chukwa runnable immediately.

I'm open to saying "the chukwa scripts should assume jars live in /build", by the way, as an alternative to moving them to CHUKWA_HOME after the build.

> Cleaner build management for chukwa-pig.jar
> -------------------------------------------
>
>                 Key: CHUKWA-288
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-288
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: build and test code
>    Affects Versions: 0.2.0
>         Environment: Redhat EL 5.1, Java 6
>            Reporter: Eric Yang
>            Assignee: Jerome Boulon
>             Fix For: 0.2.0
>
>
> The current build system generates chukwa-pig.jar in CHUKWA_HOME/contrib/chukwa-pig.  This should be changed to CHUKWA_HOME/contrib/chukwa-pig/build.  The change would prevent mangling of source file and binary file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.