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

Jetspeed

[ENH] Torque OM jar generation per backend database

Created: 18/Apr/05 01:39 PM Updated: 26/May/05 12:09 PM Due: 18/Apr/05

Return to search

Component/s:

Database

Affects Version/s:

1.6-dev

Fix Version/s:

1.6-dev

Time Tracking:

Not Specified

Resolution Date:

18/Apr/05 02:23 PM

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

David Sean Taylor made changes - 18/Apr/05 01:44 PM

Field	Original Value	New Value
Status	Open [ 1 ]	In Progress [ 3 ]

David Sean Taylor made changes - 18/Apr/05 02:23 PM

Status	In Progress [ 3 ]	Resolved [ 5 ]
Resolution		Fixed [ 1 ]

Jeremy Ford made changes - 26/May/05 12:09 PM

Summary

Torque OM jar generation per backend database

[ENH] Torque OM jar generation per backend database