Return-Path: Delivered-To: apmail-db-torque-user-archive@www.apache.org Received: (qmail 85269 invoked from network); 18 Feb 2004 14:53:06 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 18 Feb 2004 14:53:06 -0000 Received: (qmail 19997 invoked by uid 500); 18 Feb 2004 14:52:57 -0000 Delivered-To: apmail-db-torque-user-archive@db.apache.org Received: (qmail 19981 invoked by uid 500); 18 Feb 2004 14:52:56 -0000 Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Torque Users List" Reply-To: "Apache Torque Users List" Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 19954 invoked from network); 18 Feb 2004 14:52:56 -0000 Received: from unknown (HELO ProcessSystemsServer) (65.36.40.98) by daedalus.apache.org with SMTP; 18 Feb 2004 14:52:56 -0000 Received: from [10.0.1.21] by ProcessSystemsServer (ArGoSoft Mail Server Plus, Version 1.6 (1.6.0.0)); Wed, 18 Feb 2004 10:05:42 -0500 From: "Brent Atkins" To: "Apache Torque Users List" Subject: RE: trouble with Maven, MySQL & jbdc - SOLVED Date: Wed, 18 Feb 2004 09:47:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <90B3A0967470D44CB8FDE74907512328F1CE0E@av1s008.at-work.local> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hey! I took Siegfried's advice and looked at the maven-torque plugin (thanks for the tip!) and found the problem. In plugin.jelly in the create-db goal there is a call to an ant sql task (line 370). It looks like this: For some reason, the maven version of this task doesn't recognize the classpath being passed to it in this manner. All you need to do is change the code to this: As long as you make a dependency for your jdbc driver in your own POM, you are done. Up at the top of plugin.jelly it already loads your pom dependencies so nothing else needs to be changed. Everything works great now. I would submit this as a patch, but I don't really know how. If anyone would care to submit it for me or just feels like educating me on how its done I would appreciate it. Until then, enjoy! I have not tested this on the current CVS version, but I have looked at it on the web and the bug is in that version too. Since the change is so localized I can't imagine that it would break anything, but you may want to test it a bit more to be sure. -----Original Message----- From: G�schl,Siegfried [mailto:Siegfried.Goeschl@drei.com] Sent: Monday, February 16, 2004 3:17 PM To: Apache Torque Users List Subject: RE: trouble with Maven, MySQL & jbdc Hi Brent, this might not encourage you but I never got the Torque plugin working. The reason of your problem is probably the maven class loader used by the Torque plugin which usually does not pull in application dependencies during plugin execution. You should have a look at the plugin.jelly of the Torque plugin and might add your JDBC driver to 'torque-classpath' - in this case don't forget it to add your JDBC thingies to the project.xml of the Torque plugin. Don't know if this solves the problem ... please post a success story if it works .... :-) Cheers, Siegfried Goeschl --------------------------------------------------------------------- To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org For additional commands, e-mail: torque-user-help@db.apache.org