[JS1-542] [ENH] Torque OM jar generation per backend database

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6-dev
• Fix Version/s: 1.6-dev
• Component/s: Database
• Assignee: David Sean Taylor
• Reporter: David Sean Taylor
• Due: 18/Apr/05
• Created: 18/Apr/05 13:39
• Updated: 26/May/05 12:09
• Resolved: 18/Apr/05 14:23

Description

Creates torque specific bindings for the selected database.
Goal: end users will no longer have to recompile the source to get support for a different database than hypersonic. This requirement has been the source to a large number of problems reported on the user list.

on the distribution site, I'd like to provide several small jars for each torque-supported database:

+ 1.6-binary
+ torque
+ hypersonic
jetspeed-torque-om-1.6.jar
+ mysql
jetspeed-torque-om-1.6.jar
+ axion
jetspeed-torque-om-1.6.jar
+ sybase
jetspeed-torque-om-1.6.jar
...

prefer to have all the jars named the same to lessen the chance of someone accidently having 2 jars installed.