Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80270 invoked from network); 2 Jun 2005 17:41:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jun 2005 17:41:40 -0000 Received: (qmail 31428 invoked by uid 500); 2 Jun 2005 17:41:38 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 31402 invoked by uid 500); 2 Jun 2005 17:41:37 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 31389 invoked by uid 99); 2 Jun 2005 17:41:37 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from smtp812.mail.sc5.yahoo.com (HELO smtp812.mail.sc5.yahoo.com) (66.163.170.82) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 02 Jun 2005 10:41:35 -0700 Received: from unknown (HELO ?192.168.0.5?) (fuzzylogic@sbcglobal.net@68.122.237.123 with plain) by smtp812.mail.sc5.yahoo.com with SMTP; 2 Jun 2005 17:41:19 -0000 Mime-Version: 1.0 (Apple Message framework v730) In-Reply-To: <429F3F57.8010307@debrunners.com> References: <429F3F57.8010307@debrunners.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <422812AF-D7D9-492D-9C29-986895439B1B@gmail.com> Content-Transfer-Encoding: 7bit From: Andrew McIntyre Subject: Re: JSR169 status update & build/ant question Date: Thu, 2 Jun 2005 10:41:17 -0700 To: "Derby Development" X-Mailer: Apple Mail (2.730) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Jun 2, 2005, at 10:18 AM, Daniel John Debrunner wrote: > 2) Make the optional engine_169_opt target also modify the > modules.properties to add just > derby.module.jdbcJ2ME=org.apache.derby.jdbc.Driver169 The easiest way is to do something similar to how splitmessages targets are handled, or ClassSizeCatalog generation. You have one target that performs the necessary action - in this case, a , , or task which performs the necessary edit on modules.properties in the output dir - and then s a file, usually in the same location preferably with a similar name, e.g. modules.done. This target depends on a target that checks for the existence of that file and sets a property if it exists, and the execution of the original argument is dependent on that new property not being set. You could also set a property - in my example below called jsr169.available - if there is a particular resource (jar file) or classname that should be available for your jsr169 support to compile. Obviously, this should come in the build some time after modules.properties has been copied to ${out.dir}. When running clean or clobber, the .done file and the .properties file are both removed, which will cause the copy and edit to be performed at the time of the next build. andrew