Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 98200 invoked from network); 6 Feb 2010 22:28:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Feb 2010 22:28:25 -0000 Received: (qmail 92481 invoked by uid 500); 6 Feb 2010 22:28:25 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 92428 invoked by uid 500); 6 Feb 2010 22:28:25 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 92418 invoked by uid 99); 6 Feb 2010 22:28:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Feb 2010 22:28:24 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.221.194 as permitted sender) Received: from [209.85.221.194] (HELO mail-qy0-f194.google.com) (209.85.221.194) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Feb 2010 22:28:16 +0000 Received: by qyk32 with SMTP id 32so412003qyk.12 for ; Sat, 06 Feb 2010 14:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=wHenZOApC0ET8tus8vJ1JkZMtWL6BMLk7pOTGOpXIiM=; b=x2LS0kCF6ZrKtXP60SV+M6zyLXGt1stjHkYetCNepMJAjOlWpc9I6vk9LFX63SgXqx K+NCDrNvj5mhYsMduNL7J63ioTTLDk/l25HBJZ0hxMs5NiuJW4o+9tQ7p7GvkDBaHVzG A3yqAkoXEyPZryexLpbsySXEMjfE7L32Bozk8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=ldLi/nivFxK5oUyUhnsdKrmKNvhnvGOk0pCY3/EAe2Cx96kfG4fif4jcfJqnz76PJa 5Oo9Cdx1ewBTW/1fi05E3WeFS2LjY/Gh/007wPpavc3ZSXVCbkd+ZXjFECoEx+ZHoYMB APuzFTK5I6NPLQxdqRM3w5imMOTaZJctIkxao= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.229.68.11 with SMTP id t11mr8704qci.25.1265495275588; Sat, 06 Feb 2010 14:27:55 -0800 (PST) In-Reply-To: References: Date: Sat, 6 Feb 2010 14:27:55 -0800 X-Google-Sender-Auth: 4c8d20b730cb4acf Message-ID: <7c962aed1002061427h6e9c80ex4219324c95bfbdf5@mail.gmail.com> Subject: Re: Stargate War - jetty.xml and dependencies From: Stack To: hbase-dev@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Sat, Feb 6, 2010 at 3:03 AM, Paul Smith wrote: > > If someone could comment on where the jetty.xml should end up in a starga= te binary (and indeed, where it should appear in a general hbase binary tar= ball) I would appreciate it. =A0 =A0I'm guessing it's designed to be used = with Jetty to kickstart a simple app server, and assume that the generated = stargate WAR is supposed to live somewhere relative (ie. 'webapps') to be l= aunched under the /api/ context. > WAR and JAR seems a bit odd. If the JAR is for command-line tools, can't you do "java -cp X.war Command" as you would "java -cp X.jar Command"? If WAR is the target, the jetty.xml is just a convenience for case where the WAR is deployed on a jetty container? It'd be grand if the WAR could be deployed to any container -- shouldn't be a tough target to achieve if not there already (I can help w/ latter). St.Ack