Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 77926 invoked from network); 5 Jun 2010 08:26:49 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Jun 2010 08:26:49 -0000 Received: (qmail 56023 invoked by uid 500); 5 Jun 2010 08:26:48 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 55894 invoked by uid 500); 5 Jun 2010 08:26:48 -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 55887 invoked by uid 99); 5 Jun 2010 08:26:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Jun 2010 08:26:48 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com designates 209.85.161.50 as permitted sender) Received: from [209.85.161.50] (HELO mail-fx0-f50.google.com) (209.85.161.50) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Jun 2010 08:26:40 +0000 Received: by fxm1 with SMTP id 1so1560476fxm.37 for ; Sat, 05 Jun 2010 01:26:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=W2YrT3rUZwFdvYJ6YTc0M4ExXK947noIPV3QdyGVRfc=; b=PKWmQQsJU/l4fL2t5IyO4Xd3PQmAjidH72vyTrDrYH3zAgXb5cWJzmq/SBl872kXBM kirlaAu0+7VXitYyHZ8du2+J0dYA8Pt4HEE4RcUi2ZULVhZUkAR3/Xjcszl2Y3PU5Zbv 6kRg6x0nxA32vLEmkTzPcEdVcAF2RqsZY4p0Y= 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; b=plgb5a0G2qV5mQ2M3yiTSJFymq1Km+qHt/NipgDquZ6LNBdWkOaPuylRDqzNEIIa2k sCeZ5Rhhcb5BQrKNEL/C/a1w/sPnHPapEKn16FE33YBba5KkuvMRwxyZivrD2r8u2dk4 owPsHYmlqq4JLEidvZqH0wEXNH6r3lF4hGRQA= MIME-Version: 1.0 Received: by 10.223.26.206 with SMTP id f14mr12728237fac.96.1275726379898; Sat, 05 Jun 2010 01:26:19 -0700 (PDT) Sender: ayyagarikiran@gmail.com Received: by 10.223.123.79 with HTTP; Sat, 5 Jun 2010 01:26:19 -0700 (PDT) In-Reply-To: <4C0A08E7.4020309@apache.org> References: <4C0A08E7.4020309@apache.org> Date: Sat, 5 Jun 2010 11:26:19 +0300 X-Google-Sender-Auth: JFu7n82eAwRJVy7XhgnCAN2Hq_c Message-ID: Subject: Re: [ApacheDS] Module server-sar From: Kiran Ayyagari To: Apache Directory Developers List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Sat, Jun 5, 2010 at 11:20 AM, Stefan Seelmann wrote: > We have a module apacheds/server-sar. It is deactivated in the modules > section of the apacheds/pom.xml. It can't be built due to broken > dependencies. > > The pom's description states "A server archive file for ApacheDS to run > within a JBoss 3.x instance". JBoss 3.x is rather old, the latest 3.2 > release is from 2006. > > Should we delete the server-sar module? Or move it to to deceased, in > case someone wants to build a SAR for a newer JBoss version? +1, lets move it to attic Kiran Ayyagari