Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 16866 invoked from network); 8 Jan 2003 02:49:36 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 8 Jan 2003 02:49:36 -0000 Received: (qmail 11856 invoked by uid 97); 8 Jan 2003 02:50:59 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 11840 invoked by uid 97); 8 Jan 2003 02:50:59 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 11827 invoked by uid 98); 8 Jan 2003 02:50:58 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Tue, 7 Jan 2003 18:49:29 -0800 (PST) From: "Craig R. McClanahan" To: Jakarta Commons Developers List Subject: Re: [resources]&new dependant [discovery] build problems. In-Reply-To: <3E1B797F.1060707@apache.org> Message-ID: <20030107184817.H48826-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 7 Jan 2003, Robert Leland wrote: > Date: Tue, 07 Jan 2003 20:06:07 -0500 > From: Robert Leland > Reply-To: Jakarta Commons Developers List > To: Jakarta Commons Developers List > Subject: [resources]&new dependant [discovery] build problems. > > In trying to build resources, I was unable > to build it because the discovery junit tests failed > on the jelly-plugin. > I tried building discovery using both the > commons-discovery maven build, and the > commons maven build. > I can build discover just fine with "ant clean dist test.discovery". Maybe the problem has to do with some refactoring going on in Jelly at the moment? The Jelly tag libs were getting factored out of the core Jelly directory, so any external references to them might have gotten messed up. > It appears my top level build.properties for > commons is current, but then again that is only used > for direct ant builds ?!? > > If others can build discovery then I'll continue > to root around in my build environment until I find > the problem. > > -Rob > > Craig -- To unsubscribe, e-mail: For additional commands, e-mail: