chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Boulon (JIRA)" <>
Subject [jira] Commented: (CHUKWA-288) Cleaner build management for chukwa-pig.jar
Date Fri, 12 Jun 2009 18:00:07 GMT


Jerome Boulon commented on CHUKWA-288:

No, current build generate everything inside CHUKWA_HOME/contrib/chukwa-pig/build then copy
the jar file to CHUKWA_HOME/contrib/chukwa-pig the same way as pig/hadoop.

And Chukwa should be change to have the same thing. we shouldn't have to move to the build
directory to get the jar files.
The expectation is to:
- download chukwa, 
- do ant
- and run it right away from current directory,
 everything else will just not work. 

As a user I don't have to read a quick start page to learn that I have to go to build/chukwa-xxxx/
to run it.

> Cleaner build management for chukwa-pig.jar
> -------------------------------------------
>                 Key: CHUKWA-288
>                 URL:
>             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.

View raw message