Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 30444 invoked from network); 15 Jul 2007 06:16:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Jul 2007 06:16:47 -0000 Received: (qmail 16927 invoked by uid 500); 15 Jul 2007 06:16:49 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 16885 invoked by uid 500); 15 Jul 2007 06:16:49 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 16874 invoked by uid 99); 15 Jul 2007 06:16:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jul 2007 23:16:49 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Jul 2007 23:16:46 -0700 Received: by py-out-1112.google.com with SMTP id d32so1946633pye for ; Sat, 14 Jul 2007 23:16:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=TRgAD7Zk5lMPBBeVP/AMzrj1+lBJiQmIcwhgdeucyoTAGLUSIRzkUrJvAIVwEjqfR+7/DR2pS+KY3Ye8IK5BjxRnwhH6Y6sl3lPF2sa7n+qukAJwCT8dRtDhQN0yblbzshlkIK9h0XVaNF8j0Q4QjkBDIuQ35Nj/Xx0XXbq0BOs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=HEBcGtb619q4wyVKHN4ciZADXC5sSKAKtdWJcAC+K3aac3X9wzcB9MaDYUb2Jpwv8FIjbk9F+y2QjusA+Qs7fKNke2cU7k0KytlONV2Cbjp+pw04Lj4Z9u2hYp7YRESS0ckJk+TBCeyHb3+17M+dA8ADpNyMgqz7Yc9oLb8A0eM= Received: by 10.142.103.6 with SMTP id a6mr239313wfc.1184480184273; Sat, 14 Jul 2007 23:16:24 -0700 (PDT) Received: by 10.142.101.21 with HTTP; Sat, 14 Jul 2007 23:16:24 -0700 (PDT) Message-ID: Date: Sun, 15 Jul 2007 02:16:24 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Binaries for Tanuki wrapper In-Reply-To: <43b026c70707142312u5946d1ey1c8ca0d8da7ec11e@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_61202_22215877.1184480184255" References: <43b026c70707142312u5946d1ey1c8ca0d8da7ec11e@mail.gmail.com> X-Google-Sender-Auth: 2239dba57213f509 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_61202_22215877.1184480184255 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline So you're repackaging the Tanuki classes into it's own maven project? Alex On 7/15/07, Chris Custine wrote: > > Hi Everyone, > I am getting ready to commit all of the new installer and daemon code but > I have one issue that warrants debate. The Tanuki distribution contains > binaries for the daemon and Windows service wrappers, and also contains the > jar files for the bootstrapper implementations and it is not available via > Maven repository. I don't want this to be a maintenance hassle, so what I > am doing right now is expanding the distribution in a directory and using > some maven config to install the jar when you first run mvn install on the > daemon project. If I commit this the way it is on my working copy, then it > will work the same for everyone else. What I am thinking is that this will > allow us to update the distro by expanding any new versions over the top of > the old and committing the changes. > > Another option is that we could build a couple of maven artifacts with the > jar and the binaries and try to get it hosted on the maven repo. > > Any thoughts or input on what we should do here? > > Chris > ------=_Part_61202_22215877.1184480184255 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline So you're repackaging the Tanuki classes into it's own maven project?

Alex

On 7/15/07, Chris Custine < ccustine@apache.org> wrote:
Hi Everyone,
I am getting ready to commit all of the new installer and daemon code but I have one issue that warrants debate.  The Tanuki distribution contains binaries for the daemon and Windows service wrappers, and also contains the jar files for the bootstrapper implementations and it is not available via Maven repository.  I don't want this to be a maintenance hassle, so what I am doing right now is expanding the distribution in a directory and using some maven config to install the jar when you first run mvn install on the daemon project.  If I commit this the way it is on my working copy, then it will work the same for everyone else.  What I am thinking is that this will allow us to update the distro by expanding any new versions over the top of the old and committing the cha nges.

Another option is that we could build a couple of maven artifacts with the jar and the binaries and try to get it hosted on the maven repo.

Any thoughts or input on what we should do here?

Chris

------=_Part_61202_22215877.1184480184255--