Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 66405 invoked from network); 31 May 2002 19:23:31 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 31 May 2002 19:23:31 -0000 Received: (qmail 19859 invoked by uid 97); 31 May 2002 19:22:59 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 19758 invoked by uid 97); 31 May 2002 19:22:58 -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 19683 invoked by uid 98); 31 May 2002 19:22:58 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: Fri, 31 May 2002 12:22:51 -0700 Subject: Re: Driver Attribute of SQL Task should not be required Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) From: Scott Ellsworth To: "Ant Users List" Content-Transfer-Encoding: 7bit In-Reply-To: <001401c208cb$d96bd020$1219570f@ranier> Message-Id: X-Mailer: Apple Mail (2.481) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Friday, May 31, 2002, at 10:51 AM, Steve Loughran wrote: > ----- Original Message ----- > From: "Christian Wolfgang Hujer" > To: > > >> I think the driver attribute of the SQL task should be optional, not >> required. It is possible to load a JDBC Driver using the >> -Djdbc.drivers property, > > we are trying to move away from all the magic properties, so no, I > think it should stay as an attribute. Also, in my experience, the > driver is often application dependent, so that I have different drivers > for each app and the db they talk to. The nice thing about having it be a property is that you can always grab an environment variable to fill out that property within ant, and depending on how you write your build.xml, the environment can either override or be overridden by properties specified by the user. jdbc.drivers = env.jdbc.drivers which will mean that if the user sets it in user.properties, they get that one, regardless of the environment variable. By reversing the order of the property tasks, you get the other behavior. Scott -- To unsubscribe, e-mail: For additional commands, e-mail: