[
https://issues.apache.org/jira/browse/CHUKWA-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719042#action_12719042
]
Jerome Boulon commented on CHUKWA-288:
--------------------------------------
I personally don't like the idea of always running from the build directory.
The build directory contains a lot of temporary files (classes, test
cases,...), I would rather prefer to 2 configurations.
The "Dev" configuration, by default. All scripts runs out of build/classes
and/or build/contrib/<subProject>/classes.
The "Prod" configuration, you type ant dist or ant package, the dist directory
is populated with new jars (based on build/classes), build directory is
deleted. Scripts will now use jars from the dist directory. There's a hierarchy
inside the dist directory:
CHUKWA_HOME/dist/ <Chukwa's jars>
CHUKWA_HOME/dist//contrib/<SubProject>/<subProject's jars>
External jars should come from CHUKWA_HOME/lib/ or
CHUKWA_HOME/contrib/<SubProject>/lib/
conf could also be renamed to template and the real configuration will always
be generated in build/conf and moved to dist/conf for the "Production" mode
There's no longer a chukwa-xxx inside the build directory.
> 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.
