Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 86511 invoked from network); 21 Jun 2002 21:13:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Jun 2002 21:13:53 -0000 Received: (qmail 11273 invoked by uid 97); 21 Jun 2002 21:13:59 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 11257 invoked by uid 97); 21 Jun 2002 21:13: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 11245 invoked by uid 98); 21 Jun 2002 21:13:58 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Authentication-Warning: costinm.sfo.covalent.net: costin owned process doing -bs Date: Fri, 21 Jun 2002 14:12:59 -0700 (PDT) From: costinm@covalent.net X-X-Sender: costin@costinm.sfo.covalent.net To: Jakarta Commons Developers List Subject: Re: unmavenising Commons projects In-Reply-To: <022401c21964$7463b270$0111010a@user> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I don't remember seeing any proposal or vote on requiring maven for the builds of commons components. Given the goals of commons I think it is completely wrong to add those requirements without a formal proposal. We do have a requirement minimising external dependencies, and the commons components must be built and used by people who use a variety of build systems. Again, I have nothing against providing an optional build file for maven and/or centipede - but I think it is a very serious issue if commons components can't be built with plain ant and minimal pain. Costin On Fri, 21 Jun 2002, Juozas Baliuka wrote: > Hi, > Is it some trivial way to setup maven for user ? > Something like this: > 1. user downloads project. > 2. types ant. > 3. if Maven is not present, some ant task downloads and installs it (says > "Do you want to .." before). > 4. Maven downloads dependencies and builds project. > > > > ----- Original Message ----- > From: "Jason van Zyl" > To: "Jakarta Commons Developers List" > Sent: Friday, June 21, 2002 8:32 PM > Subject: RE: unmavenising Commons projects > > > > On Fri, 2002-06-21 at 14:22, Henri Yandell wrote: > > > Mainly: > > > > > > 1) Maven is in rapid development. When b5 is released, it will mean > > > upgrading all Commons projects. > > > > That's not true. With b5 a build.xml file won't be required so > > delegators won't have to be twiddled with and though it is in continuing > > development the auto updating facility does work. One of the primary > > goals of Maven is to make the transition easier but in this last burst > > of changes people have moved ahead of the b4 release which does cause > > problems. > > > > > 2) I see no documentation in the Commons projects telling me which > version > > > of Maven we need. Furthermore, I don't believe it is at all easy to run > > > multiple versions of maven as the same user. > > > > It should be handled for you automatically but if this isn't working > > then we can work something out. Having multiple versions of Maven > > installed will definitely happen and we need to deal with it. > > > > > 3) There is no need to use build.xml with Maven anymore. By rolling them > > > back we can have both the old system and the new system working fine. > > > > For b5 the build.xml file won't be necessary and then there can be a > > complete legacy build.xml file. But it should be generated from the > > project descriptor. At that point we could probably add something to > > generate the legacy build when the project.xml file changes. > > > > > Hen > > > > > > On Fri, 21 Jun 2002, Brekke, Jeff wrote: > > > > > > > -1, why go back? I don't understand what the problem is. > > > > > > > > ================================================================= > > > > Jeffrey D. Brekke Quad/Graphics > > > > Jeff.Brekke@qg.com http://www.qg.com > > > > > > > > > > > > > -----Original Message----- > > > > > From: Henri Yandell [mailto:bayard@generationjava.com] > > > > > Sent: Friday, June 21, 2002 1:13 PM > > > > > To: Jakarta Commons Developers List > > > > > Subject: unmavenising Commons projects > > > > > > > > > > > > > > > Currently we have 10 mavenised projects [to my tallying]. > > > > > > > > > > commons: > > > > > > > > > > cli > > > > > configuration > > > > > email > > > > > graph2 > > > > > jelly > > > > > net > > > > > util > > > > > xo > > > > > > > > > > commons-sandbox: > > > > > > > > > > betwixt > > > > > cli > > > > > > > > > > I'm concerned that these changes happened to the build.xml > > > > > files making > > > > > those projects require Maven. I'd like to suggest that we > > > > > restore the old > > > > > build.xml and add a build-maven.xml file as is suggested in the > Maven > > > > > documentation. > > > > > > > > > > Or that we just roll these build.xml's back and use a script like > the > > > > > maven2 script. > > > > > > > > > > Hen > > > > > > > > > > > > > > > -- > > > > > To unsubscribe, e-mail: > > > > > > > > > > For additional commands, e-mail: > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > > > For additional commands, e-mail: > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > > For additional commands, e-mail: > > > -- > > jvz. > > > > Jason van Zyl > > jason@apache.org > > http://tambora.zenplex.org > > > > In short, man creates for himself a new religion of a rational > > and technical order to justify his work and to be justified in it. > > > > -- Jacques Ellul, The Technological Society > > > > > > -- > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: