Issue Details (XML | Word | Printable)

Key: SAK-12031
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Jim Eng
Reporter: Jim Eng
Votes: 0
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Sakai

Conversion utility should be in database project

Created: 23-Oct-2007 15:11   Updated: 23-Oct-2008 06:30
Component/s: Assignments, Content service (Pre-K1/2.6), Database service (Pre-K1/2.6)
Affects Version/s: 2.5.0
Fix Version/s: 2.5.0

Time Tracking:
Not Specified

Issue Links:
Relate
 

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
The conversion utility classes are duplicated in assignments and content. They should be in database, with the config files and handlers in the project whose tables are being converted.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Ian Boston added a comment - 23-Oct-2007 16:55
Done,

You need to test both assignments and content,
there is a new script in db/db-util/conversion/runconversion.sh that is a generic script that allows you to run the framework and add your implemenation jars in on the command line.

I have also don assignments, but this all needs to be moved to 2.4.x as well.

Megan May added a comment - 29-Oct-2007 13:06
Merged into 2.5.x

Megan May added a comment - 31-Oct-2007 05:32
Fixes included in 2.5.0.011 tag

Jim Eng added a comment - 14-Nov-2007 09:15
Once we merge the conversion for trunk to post-2.4, this issue will also affect post-2.4. The question is whether this change should also be applied to post-2.4? Should we add the conversion utility to content in post-2.4 and then move it to db?

David Haines added a comment - 14-Nov-2007 09:26
Would this require changes to other projects?

David Haines added a comment - 14-Nov-2007 10:13
Is this just the cleanup of a duplication or is it causing errors?

Megan May added a comment - 06-Feb-2008 11:59
Tasks for 2.5.0 have been completed. We're nearing the end of the QA cycle and A lot of general regression testing has been going on for the past few months - the changes have likely been reviewed via this method of testing