You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Dave DeMaagd (JIRA)" <ji...@apache.org> on 2013/01/24 20:35:12 UTC
[jira] [Created] (KAFKA-733) Fat jar option for build, or override
for ivy cache location
Dave DeMaagd created KAFKA-733:
----------------------------------
Summary: Fat jar option for build, or override for ivy cache location
Key: KAFKA-733
URL: https://issues.apache.org/jira/browse/KAFKA-733
Project: Kafka
Issue Type: Improvement
Components: packaging
Affects Versions: 0.8
Reporter: Dave DeMaagd
Need some kind of self-contained mechanism for running kafka to get around the following:
1) The location of the source checkout/build is not necessarily the same place where it will be running (the build location and that user's ivy cache dir) potentially leading to sync problems (forgetting the ivy dir) or just adding overhead to the deployment process (additional steps to remember introduces more chances for mistakes)
2) The user running the kafka service in a production setting may not even have a real home directory
Think something like a 'fat jar' packaging (something that contains all necessary jar versions in one convenient place) would simplify deployment and reduce the chance for error (only one lib package to worry about, and it contains everything needed) and would be a little more production friendly
--
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