During deployment, i agree this is a better solution. For some tasks during build operation (e.g., db tests, import PSML files to db, etc...) I really need to tell maven about my drivers and other external jar files. So I think I need the first solution you mentioned. However, I thought there is a better way of doing it without modifying the configuration files.
Anyway, your suggestions help a lot. Thanks! Quoting Stijn de Witt <[EMAIL PROTECTED]>: > I just thought of another solution. Place the driver jar in a shared lib > directory of your application server. For tomcat this is shared/lib if I > remember correctly. > The advantages of this method are that you don't have a copy of the driver > in each and every webapp on the server, and that your jetspeed project > doesn't have to 'know' what database it is using. Also, this way you don't > have to modify project.xml... > > -Stijn > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
