Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 1343 invoked from network); 22 Feb 2002 14:29:50 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Feb 2002 14:29:50 -0000 Received: (qmail 5783 invoked by uid 97); 22 Feb 2002 14:29:42 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 5722 invoked by uid 97); 22 Feb 2002 14:29:41 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 5659 invoked from network); 22 Feb 2002 14:29:38 -0000 Message-ID: <8A6F09AD8049134282148A453CB93B9A016040B8@roc-mail1.xelus.com> From: "Schaefer, Don" To: 'Ant Users List' Subject: RE: use cases request Date: Fri, 22 Feb 2002 09:28:49 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1BBAD.3E61AED0" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C1BBAD.3E61AED0 Content-Type: text/plain; charset="iso-8859-1" For the last use case - handling differences between products we have gone a different route. I am sure that other have done something similar as well. We express the elements we need generically in our "component descriptor". These elements include: -queues, system properties, jdbc connection pools,classpaths, ejbs, wars, directory creation, html, xsl etc. We then have a transforms for the products that we deliver to: wls51, was401 sse, wls61 and (hopefully soon) jboss. This allows us to handle the many differences between the products we support. But I second the vote for property merge as well as preserving comments. Thanks for all your work, don. -----Original Message----- From: Phil Surette [mailto:psurette@espial.com] Sent: Wednesday, February 20, 2002 9:47 AM To: 'Ant Users List'; ant-dev Subject: RE: use cases request I use propertyfile but none of the funky stuff you're worrying about. However, if you're interested in feature requests ;) - it would be very nice if propertyfile would preserve comments etc. This is already mentioned in the task documentation as a nice-to-have. I've looked around the web and can't find any utility for editing property files that you could use and have considered writing one. Right now I'm trying to polish up a set of Jython task definitions however. - I would also like a property file merge type operation where the contents of one property file could be added to another property file and override any shared properties. Basically what I want is a sort of inheritance for property files. My use case for this is related to managing configuration files for multiple j2ee containers. I have a common properties file that contains things like jdbc driver names, topic and queue names etc. But jboss and weblogic have different naming conventions for some of these things, one container will need an extra configuration parameter, different versions of the same container will have some differences, so I want to do a merge like this: container.properties overridden and extended by jboss.properties overridden and extended by jboss244.properties The result of this is applied via a copy/with/filterset operation to jboss244 filter configuration files. -----Original Message----- From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] Sent: Wednesday, February 20, 2002 8:23 AM To: ant-dev; ant-user@jakarta.apache.org Subject: use cases request I'm knee-deep in refactoring to actually work in as many cases as I can envision. It has been in several states of disrepair in the past and I'm trying to fix it so that defaults and operations all work as expected. There is some odd code in there that allows operations besides "+", "-", and "=" and I'm wondering if anyone ever used these. They are not documented for the 'operation' attribute and I plan on removing them. Are folks using date operations with ? If so, could you send me some samples of how you are using it so that I can roll those into the test cases? I'm not quite sure how the date operations should be specified. It looks as though if 'value' is used in conjuction with 'type="date"' and 'operation' then the value attribute is taken as a date (Calendar to be more precise) and then added or subtracted from the actual value. It seems odd to apply those kinds of operations on two dates, but maybe I'm missing something. You don't really add one date to another, you add days, or hours, or years. Is there some other API that I should be looking into for date operations so that 'value' is not pulled in as a Calendar object when an operation is specified? What does a date of "never" do? Why would you ever use it? Is it just a placeholder for an unknown date? Again, send me use cases, especially if doing date operations. If you don't then risk me breaking it! :) Thanks, Erik -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: ------_=_NextPart_001_01C1BBAD.3E61AED0--