Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Sat, 23 Feb 2013 21:14:12 +0000 (UTC)
From: "Joe Stein (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12629128.1359056027663.328899.1361654052731@arcas>
In-Reply-To: <JIRA.12629128.1359056027663@arcas>
References: <JIRA.12629128.1359056027663@arcas>
Subject: [jira] [Commented] (KAFKA-733) Fat jar option for build, or
 override for ivy cache location
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KAFKA-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585214#comment-13585214 ] 

Joe Stein commented on KAFKA-733:
---------------------------------

I like the idea of assembly but not everyone is going to want/like another dependency so we adding a dependency for running the server without providing another option.   

In either case something has to get done here KAFKA-760 for how to star the server for different build options this would be another option
                
> 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
>            Assignee: Dave DeMaagd
>              Labels: bugs
>         Attachments: KAFKA-733.patch
>
>
> 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