Return-Path: Delivered-To: apmail-jakarta-taglibs-dev-archive@jakarta.apache.org Received: (qmail 2443 invoked by uid 500); 12 Jul 2001 16:00:17 -0000 Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: taglibs-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list taglibs-dev@jakarta.apache.org Received: (qmail 2288 invoked from network); 12 Jul 2001 16:00:11 -0000 Received: from smtp012.mail.yahoo.com (216.136.173.32) by h31.sny.collab.net with SMTP; 12 Jul 2001 16:00:11 -0000 Received: from host62-6-127-132.host.btclick.com (HELO lndevjs) (62.6.127.132) by smtp.mail.vip.sc5.yahoo.com with SMTP; 12 Jul 2001 16:00:12 -0000 X-Apparently-From: Message-ID: <033a01c10aeb$9a57c440$9865fea9@spiritsoft.com> From: "James Strachan" To: References: <00d101c10ab7$e5753040$9865fea9@spiritsoft.com> <3B4D8066.15043336@optonline.net> <028701c10ad8$dc6450a0$9865fea9@spiritsoft.com> <3B4DB6F8.AE8CC51C@optonline.net> Subject: Re: using jjar (was Re: thoughts on new builds (was: Re: [UPDATE]Converting existingtaglibs to use new build)) Date: Thu, 12 Jul 2001 16:59:14 +0100 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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N From: "Geir Magnusson Jr." > > I'll gladly help all I can integrating jjar into the jakarta-taglibs build > > process (as an optional target). > > How do you see it working? In just the build process, or at runtime? I think for now, just a build process that can download all the required jars to a local directory somewhere will do. So then if a developer wishes to build the jakarta-taglibs for the first time they could do build download (then jjar kicks off, downloading local copies of all the required jars into a local repository) build dist (now do a build as we've got the jars somewhere). Then the default build.properties could contain links to where the jars will be downloaded to. So the build would just run out of the box by default. If a user didn't want to use jjar but would rather use their own jars elsewhere, they could provide their own build.local.properties to override the defaults in build.properties. > My vision for this kind of stuff is to see how far we can push > runtime-ish stuff... However, the build process use is easy, as it's > just another use of runtime... Agreed. I'm interested in the runtime side of things too - though probably not for the jakarta-taglibs build. Lets keep those thoughts for jakarta-commons. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com