Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 1602 invoked from network); 17 Jul 2002 16:51:10 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 Jul 2002 16:51:10 -0000 Received: (qmail 10155 invoked by uid 97); 17 Jul 2002 16:51:24 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 10082 invoked by uid 97); 17 Jul 2002 16:51:23 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 10067 invoked by uid 98); 17 Jul 2002 16:51:23 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <04fb01c22db2$5fa458f0$1219570f@ranier> From: "Steve Loughran" To: "Ant Developers List" References: Subject: Re: Splitting up optional.jar Date: Wed, 17 Jul 2002 09:52:45 -0700 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Stefan Bodewig" To: Sent: Wednesday, July 17, 2002 2:38 AM Subject: Splitting up optional.jar > I'd like to split optional.jar into several pieces: > > * optional-nodeps.jar - all stuff which doesn't require any external > code or only depends on the JVM in use. This one can savely live on > the system classpath. > > I'm a little stretched when it comes to the Swing dependency. Should > this be placed into a separate jar as one could install javax.swing > for JDK 1.1 (and probably even Kaffe?). > > * optional-trax.jar - all stuff that requires TraX interfaces. > > * optional-weblogic.jar - this would combine all three weblogic > conditional patternsets. > > * optional-antlr.jar > * optional-bsf.jar > * optional-icontract.jar > * optional-jakarta-bcel.jar > * optional-jakarta-commons-logging.jar > * optional-jakarta-log4j.jar > * optional-jakarta-oro.jar > * optional-jakarta-regexp.jar > * optional-javamail > * optional-jdepend.jar > * optional-jmf.jar > * optional-junit.jar > * optional-netcomponents.jar > * optional-netrexx.jar > * optional-starteam.jar > * optional-stylebook.jar > * optional-vaj.jar > * optional-xalan1.jar > * optional-xalan2.jar > * optional-xslp.jar > > should be self-explaining. > > Are there any better names? 1. I understand why you are breaking it up by dependency, but IMO it should be broken up by functionality, and each jar can have its own dependencies (or not) examples ant-networking: netcomponents, maybe later httpclient ant-dotnet, ant-clearcase, ant-perforce, ant-vss: only external app dependencies ant-xml: the xml suite of stuff etc. This makes it more obvious what antlib you need to run a particular task. 2. we need ant version numbers in the jar titles, of course, to stop version confusion. The risk is we introduce a new bugrep "I am running ant1.7 but the task doesnt support the option authmode="liberty""; the cause being they have the ant1.6 version of this (hypothetical) task on the cpath. 3. we need a manifest to handle versions and dependencies; it could be the normal manifest, or it is our own XML descriptor. 3. -- To unsubscribe, e-mail: For additional commands, e-mail: