Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 6290 invoked by uid 98); 21 Jan 2003 15:41:12 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 5957 invoked from network); 21 Jan 2003 15:41:06 -0000 Received: from unknown (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 21 Jan 2003 15:41:06 -0000 Received: (qmail 36910 invoked by uid 500); 21 Jan 2003 15:39:23 -0000 Received: (qmail 36863 invoked from network); 21 Jan 2003 15:39:22 -0000 Received: from smtp016.mail.yahoo.com (216.136.174.113) by 208.185.179.12.available.above.net with SMTP; 21 Jan 2003 15:39:22 -0000 Received: from pc-80-193-217-22-hw.blueyonder.co.uk (HELO lndevjs) (james?strachan@80.193.217.22 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 21 Jan 2003 15:39:23 -0000 Message-ID: <04fb01c2c163$2a1ea650$9865fea9@spiritsoft.com> From: "James Strachan" To: "Jakarta Commons Users List" References: <033001c2c14e$89584af0$9865fea9@spiritsoft.com> Subject: Re: [jelly] classpath issues (was Re: [jelly] value-of ??) Date: Tue, 21 Jan 2003 15:38:35 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N From: "Paul Libbrecht" > Currently trying to reproduce this and... had to move the > installation to another computer so... of course... the classpath had > to be reconfigured, as guessed, it was DOM-4j-dev-7 that I was using. > I'll dig more when I'm through with this test... > > The general question of classpath is a slight (or a big?) trouble: > I'd like to keep the dependencies as small as possible so I am just > using a file to store all the jars that I want to use (and not make > "all jars in repository" like in the maven-generated build.xml, it > includes several versions of, e.g. DOM 4j !!). The recent refactoring of the Jelly build system should have fixed this now. e.g. you could just build the XML library for Jelly using only the jars it requires to build and run the unit tests. > This file is hand produced when I need it. But I realize now that I > will not get an update of the classpath (I did not get it in my case). > > How to maintain an up-to-date classpath for Jelly ? > I fear this is closer to a maven debate. You're right :-) I use CVS HEAD of Maven to build Jelly libraries and run the unit tests. Or add Maven targets to run certain sample programs. e.g. take a look at the maven.xml for the swing library which has a number of targets for running demo applications in a forked JVM using the classpath from the Maven dependencies as well as including the java and test code in the classpath too. http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/jelly/jelly-tags/swing /maven.xml?rev=HEAD James ------- http://radio.weblogs.com/0112098/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com