Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 43473 invoked from network); 15 Aug 2005 06:14:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Aug 2005 06:14:02 -0000 Received: (qmail 69126 invoked by uid 500); 15 Aug 2005 06:14:00 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 69045 invoked by uid 500); 15 Aug 2005 06:14:00 -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 69031 invoked by uid 99); 15 Aug 2005 06:14:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Aug 2005 23:14:00 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of brett.porter@gmail.com designates 64.233.184.207 as permitted sender) Received: from [64.233.184.207] (HELO wproxy.gmail.com) (64.233.184.207) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Aug 2005 23:14:19 -0700 Received: by wproxy.gmail.com with SMTP id 55so931872wri for ; Sun, 14 Aug 2005 23:13:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IAxthz/xHOEo70n1YRK9SbPgbZ3cC3IsafSyQvuw8SrKENR8C4X5Xn/e2YI7ycrtPhnPSZs2HyVHQQardu9WjhEuVjVRuCuLQ5sEDF/3kfBeJSbcXKTeS6fPowqaG/ExufEOUhbDWTiE7teRrVyl0mWFOABaSkNdQC39maiKfTE= Received: by 10.54.83.5 with SMTP id g5mr3452279wrb; Sun, 14 Aug 2005 23:13:57 -0700 (PDT) Received: by 10.54.42.42 with HTTP; Sun, 14 Aug 2005 23:13:57 -0700 (PDT) Message-ID: <9e3862d805081423132be2dda@mail.gmail.com> Date: Mon, 15 Aug 2005 16:13:57 +1000 From: Brett Porter To: Gump code and data Subject: Re: temporarily disable nags for Directory in gump? Cc: Apache Directory Developers List In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <9e3862d80508141609297ad1b6@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 8/15/05, Leo Simons wrote: > Would you like access?=20 If you trust me to poke around without damaging anything when a project goes down, I'm happy to go in and fix it again - sure. > Heck, would you like to be on the Gump PMC? I have to admit my interests lay with getting projects to play together more than the implementation of gump itself, so I'm not sure I could do that justice :) (also not sure if you are serious :) > leosimons@vmgump:/usr/local/gump/public/workspace/directory-naming$ svn > cleanup > svn: '' is not a working copy directory >=20 > Could you be more specific? I was just going off of: http://vmgump.apache.org/gump/public/apacheds/gump_work/update_apacheds.htm= l naming is fine, but appears to be under a cvs subdirectory of workspace: http://vmgump.apache.org/gump/public/gump_repo/gump_work/update_directory-n= aming.html > If that's what you really want. Just comment out the elements in t= he > descriptors and no e-mail will be sent. Ok, we can discuss that at greater length on directory-dev. I just wanted to get your opinion on the matter. > I'll point out that in general if your build "keeps breaking" (rather tha= n > being broken all the time) that's because it keeps changing in > non-compatible ways. I know I've always have had loads of trouble getting= it > all to compile everytime I tried to look at it. Directory does have a > problem there. Agreed - that should settle as the individual parts stabilise. But as they chase each others development it will be a problem without a monolithic build. Again, I might put this to the list as a separate item. There is an additional problem in having to maintain two descriptors, which seems to be where a lot of the breakages come from. The addition of dependencies is often needing to be hunted down and added to gump. That could also be viewed as a good thing to take addition of dependencies more seriously, but a hassle when its already been well considered. I guess the thing about it is that even if it isn't a big deal, it is annoying that a perfectly legitimate build will break under gump. > Oh, and the second bit I'll mention is that it seems no-one ever pays > attention to the builds for their project unless they get e-mail, so > there'll probably be a 'hump' to get over once you get back to sending > yourself e-mail :-) So densensitized to warning mails now, that I think that's an issue either way :) > There's a few example of bigger maven-based builds (for example I know ab= out > Excalibur) that tend to build fine. Yep, I don't think there is anything wrong with the Maven support. > Mind you -- that's still going to be a while. for gump3, sure - but hopefully some other projects will find directory stuff useful soon. I've already seen talk of MINA on the incubator list today... Thanks for your feedback Leo. - Brett