Opened 15 years ago

Closed 14 years ago

Last modified 14 years ago

#358 closed enhancement (fixed)

Better info from Migration tool

Reported by: Nicklas Nordborg Owned by: Martin Svensson
Priority: major Milestone: BASE 2.4
Component: migrate Version:
Keywords: Cc:

Description (last modified by Martin Svensson)

The output of the migration tool is somewhat sporadic and not very inconsistent. It should be made to use the log4j logging system in a better way. We should use the various log levels (debug, info, warn, error) to control output.

  • debug - output some info about every item transfered, ie. name, BASE 1 ID, BASE 2 ID
  • info - output info when a transfer is started and ended for each type, could perhaps be useful also to put in some summary in end-info
  • warn - output info if an item couldn't be connected to an optional item, for example, a missing protocol for a sample, etc. A sensible default should be used for missing links.
  • error - If an item could not be migrated due to some other problems

The default log level should be warn.

Change History (12)

comment:1 Changed 15 years ago by Nicklas Nordborg

Component: webmigrate

comment:2 Changed 15 years ago by Jari Häkkinen

Milestone: BASE 2.x+BASE 2.4

comment:3 Changed 15 years ago by Jari Häkkinen

Milestone: BASE 2.4BASE 2.3

Milestone BASE 2.4 deleted

comment:4 Changed 14 years ago by Martin Svensson

Owner: changed from Nicklas Nordborg to Martin Svensson
Status: newassigned

comment:5 Changed 14 years ago by Martin Svensson

Description: modified (diff)

comment:6 Changed 14 years ago by Martin Svensson

(In [3496]) References #358. Started to implement a log-structure in the migration tool.

comment:7 Changed 14 years ago by Martin Svensson

(In [3508]) References #358. Use log4j properly in migration.

comment:8 Changed 14 years ago by Martin Svensson

(In [3525]) References #358. Use log4j properly in migration. Updated more files...

comment:9 Changed 14 years ago by Martin Svensson

(In [3529]) References #358. Use log4j properly in migration. Updated more files... The generated log-output still needs to be analyzed

comment:10 Changed 14 years ago by Martin Svensson

(In [3531]) References #358. Some changes on the log statements

comment:11 Changed 14 years ago by Martin Svensson

Resolution: fixed
Status: assignedclosed

(In [3532]) Fixes #358 Better info from migration tool

comment:12 Changed 14 years ago by Nicklas Nordborg

(In [3635]) References #358: Better info from Migration tool

Show log message when BASE 1 file doesn't exist on server

Note: See TracTickets for help on using tickets.