Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 18682 invoked from network); 24 Jun 2002 13:48:28 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 24 Jun 2002 13:48:27 -0000 Received: (qmail 24126 invoked by uid 97); 24 Jun 2002 13:48:32 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 24084 invoked by uid 97); 24 Jun 2002 13:48:31 -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 24071 invoked by uid 98); 24 Jun 2002 13:48:31 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-Id: <5.0.2.1.0.20020624152421.03309008@localhost> X-Sender: baliuka/taurus.mediaworks.lt@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 24 Jun 2002 15:51:19 +0200 To: "Jakarta Commons Developers List" , Jakarta Commons Developers List From: Juozas Baliuka Subject: Re: unmavenising Commons projects In-Reply-To: References: <1024911873.18098.31.camel@oasis> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Yes, it is good to have common process to build commons, I prefer minimalism for building, it is very good to have tools for site generation and dependency download, but they must not be a dependency to build "jar" or to run tests. Users and contributors must be able to build code and to run tests as trivial as possible. At 08:16 2002.06.24 -0500, Michael A. Smith wrote: >On 24 Jun 2002, John Keyes wrote: > > Folks the discussion here should not be about what GUMP is or > > what Maven is. It should be about standardizing the build > > process for Commons. > >Hmmm... Maybe I should have been paying more attention to this thread. >I didn't realize there was talk about standardizing build process for >all of commons. > > > It seems that the general consensus is that to satisfy all > > parties there should be two ant projects, build.xml and > > build-maven.xml. Could this issue be resolved with just one > > project, build.xml. > > > > The default target for this project must generate the binary > > distribution. If the default target is 'dist' then both scenarios > > could be accomodated as follows: > >I'm not so sure about tha. Currently, collections has the tests run as >the default project (compiling anything as necessary). I feel it's a >good thing to have the full test suite run by default, and I wouldn't >want that to change > > > > > > > > > ... > > > > > > > > ... > > > >regards, >michael > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: